What is an example of a data check for the FMS database before flight?

• A. Ignore the database and rely on charts.
• B. Update the database last flight.
• C. Use unverified user-provided routes.
• D. Confirm database date/version; cross-check route/waypoints against official charts; ensure database integrity.

Answer: (D)

Verifying the FMS nav data before flight centers on ensuring the data you're loading is current, accurate, and consistent with official sources. Start by confirming the database date or cycle so you’re using the correct update level. Then cross-check the planned route and each waypoint against official aeronautical charts to catch any discrepancies, such as deprecated fixes, renamed points, or routing that doesn’t match charted procedures. Finally, run integrity checks on the database to confirm there are no data corruptions and that the route can be loaded and sequenced correctly in the system.

This approach keeps navigation data aligned with published information and protects against autonav or waypoint errors in flight. Skipping these checks, relying on outdated data, or accepting user-provided routes without verification can lead to mismatches, loading problems, or unsafe routing.