Launching Q1 2027. Join the waitlist for early access.
Guide

Surviving a National Simulator Program (NSP) evaluation — what to bring

The NSP's annual evaluation can ground your simulator if you fail. This is the practical preparation guide — what the evaluators look for, what trips operators up, and how to keep your Level D qualification clean.

~11 min readUpdated 2026-05-255 sections

What is the National Simulator Program?

The National Simulator Program (NSP) is the FAA's centralized simulator-qualification authority, based at the Atlanta Aircraft Evaluation Group. The NSP issues each simulator a Qualification Letter (Level A through D for FFS, Level 4 through 7 for FTDs) and re-evaluates the device on a 12-month recurring cycle.

Initial qualification involves on-site evaluation by NSP examiner pilots and engineers; recurring qualification follows the same template at a lighter touch. A simulator that fails recurring evaluation can be downgraded (Level D → C) or pulled from service entirely.

What NSP evaluators check (in this order)

Documentation review comes first. Evaluators read the Master Qualification Test Guide (MQTG), Operations Specifications (OpSpecs), and the simulator's discrepancy log going back to the last evaluation. Discrepancies that should have been MEL'd but weren't are the most common red flag.

Objective tests follow. The evaluator runs each test in the MQTG and compares simulator response against the validated aircraft data file. Tolerance bands are tight — a misalignment outside ±2 knots indicated airspeed during a take-off run is enough to flag.

Subjective testing comes last. An NSP examiner pilot flies a representative profile (typical approach, missed approach, V1 cut, etc.) and rates the simulator on handling fidelity, sound, visual cues, motion cueing, and instructor station performance.

  • Documentation review (MQTG, OpSpecs, discrepancy log, configuration history)
  • Objective tests (MQTG procedure-by-procedure against aircraft data file)
  • Subjective testing (NSP pilot ride, handling + fidelity rating)
  • Maintenance program audit (preventive + corrective records)
  • Instructor station functionality (per-feature exercise of the IOS)

Most-cited categories (where operators fail)

Discrepancy log management is the #1 source of citations. NSP wants every malfunction tracked from observation through to root-cause and signed-off resolution. Operators that close discrepancies without an engineering signoff get cited.

Configuration management is #2. Every software/firmware change to the simulator's host computer, visual generator, or instructor station should be documented with a configuration-management number, FAA approval if it changes a qualified function, and an objective re-test if it touches simulation-of-flight data.

MQTG currency is #3. The MQTG must reflect the simulator's current state. A re-evaluation that finds the MQTG and the live device out of sync is an automatic downgrade risk.

What to have ready before the NSP team lands

Operators that pass cleanly have a single binder (or digital folder) that the evaluators can navigate without help. The package contains: current Qualification Letter, current OpSpecs, MQTG with every test result file, full discrepancy log since the last evaluation (open + closed), maintenance program records, instructor authorization records (if NSP is paired with an annual POI visit), and the simulator's training utilization data.

Pro tip: keep the Qualification Test Guide tests pre-printed and labeled with what state the simulator should be in before the evaluator presses 'go.' Saves 4-6 hours during the visit.

How software helps you keep NSP-ready

AviationAlley tracks NSP next-due dates per simulator with auto-rolling 12-month intervals. The compliance page surfaces sims approaching their NSP window 60 / 30 / 15 days out. Every maintenance log entry, work order, and discrepancy is timestamped with actor + reason — the evaluator-ready audit trail builds itself.

The FAA inspection mode at /app/inspection produces a read-only navigation surface evaluators can move through without a chaperone. POI / PMI / NSP visits all use the same flow.

Frequently asked questions

How long does an NSP evaluation take?

Recurring evaluations: 1–2 days per simulator. Initial qualifications: 3–5 days. The variance depends on simulator complexity and how well the documentation package is organized.

Can a simulator be downgraded mid-cycle?

Yes — outside the regular 12-month cycle, NSP can issue an Emergency Order of Investigation if a serious safety issue is reported. This is rare but consequential. Downgrades can also happen after a recurring evaluation if objective testing fails.

What's the cost of an NSP evaluation?

Operators pay travel + per diem for the NSP team plus a small evaluation fee. Budget $8K–$15K per simulator-day for a recurring evaluation when factoring in operational downtime.

Does AQP affect the NSP cycle?

No. AQP is a Part 121 program governance framework; NSP is a hardware-qualification regime. They're independent. A Part 142 center can run AQP-aligned training on any qualified simulator.

Related guides

From guide → operating reality.

AviationAlley ships the software patterns described in this guide — audit-grade logging, module-gated FAR enforcement, AAIP-friendly maintenance program tracking.