How do you verify the accuracy of the FMS database in the Longitude 700 before flight?

• A. Check database date/version, cross-check route/waypoints against official charts, ensure database integrity.
• B. Rely on pilot memory for route data.
• C. Update the database during the flight.
• D. Ignore database date/version.

Answer: (A)

Verifying FMS nav data before flight centers on currency, alignment with published charts, and data integrity. You want to confirm the navigation data you’ll rely on is current, matches the official publications, and is free from corruption.

First, check the database date and version to ensure you’re using the latest navigation cycle. This tells you that fixes, airways, and procedures reflect recent changes. Using an out-of-date cycle can mean the aircraft is navigating with obsolete information, which is risky.

Next, cross-check the route and waypoints loaded in the FMS against official charts and the filed flight plan. This step catches discrepancies such as deprecated or renamed waypoints, mismatched airways, or routing that doesn’t reflect the published material, ensuring the FMS route will align with what you intend to fly.

Finally, verify database integrity. This involves confirming there are no corrupted records, missing entries, or checksum failures in the nav data, so the FMS won’t misread or fail to load necessary nav fixes during operation.

Relying on pilot memory for route data is unsafe, updating the database during flight isn’t appropriate, and ignoring the database date/version ignores critical currency—each of those can lead to navigation errors or unexpected deviations.