Part 142 · Simulator & scheduling

Device inventory

Every device — Full Flight Simulator Level A–D, FTD, AATD, BATD — is one record carrying its operational status. FFS and FTD carry a real Part 60 qualification level (Level A–D / Level 4–7); AATD and BATD aren't Part 60-qualified at all — they're approved through a separate Letter of Authorization (LOA) under 61.4(c), and the record tracks that instead. The schedule, utilization, and NSP cycles all hang off the same record, so a device's status and eval window never live in two different places. It replaces the device list taped to the scheduling office wall.

Join the waitlist Request a demo

Launching the first quarter of 2027.

Training devices

FFS A–D · FTD · AATD · BATD · one record each

Devices

Operational

In maintenance

DeviceModelQual levelStatus

FFS-01B737-800FFS Level DOperational

FFS-02A320FFS Level DOperational

FTD-04B737 FTDFTD Level 6Sched. maint.

AATD-1C172 AATDAATDOperational

Schedule, utilization, and NSP cycles hang off the same record

Illustrative — every screen reflects your own data.

Who it's for

Schedulers and the director of training at a Part 142 center who need every device's qualification level (or LOA, for AATD/BATD) and status in the one place the rest of the platform reads from.

What it replaces

The device list taped to the scheduling office wall and the separate spreadsheet that tracks each sim's qual level and eval window.

What device inventory gives you

FFS Level A–D, FTD, AATD, and BATD on one record
FFS/FTD carry a Part 60 qualification level; AATD/BATD track an LOA instead
Schedule, utilization, and NSP cycles hang off the same record

One record per device, qualification or LOA included

Every training device — a Full Flight Simulator from Level A through D, an FTD, an AATD, or a BATD — is a single record carrying its current operational status. FFS and FTD carry a genuine Part 60 qualification level; AATD and BATD are approved through a separate Letter of Authorization (LOA) under 61.4(c), and the record tracks that instead of a Part 60 level. Add each device once, and the status it carries is what the floor and the schedule reflect, so a device is never described one way on a wall list and another way in a spreadsheet.

FFS Level A–D, FTD, AATD, and BATD on one record
FFS/FTD qualification level or AATD/BATD LOA, plus operational status

Training devices

FFS A–D · FTD · AATD · BATD · one record each

Devices

Operational

In maintenance

DeviceModelQual levelStatus

FFS-01B737-800FFS Level DOperational

FFS-02A320FFS Level DOperational

FTD-04B737 FTDFTD Level 6Sched. maint.

AATD-1C172 AATDAATDOperational

Schedule, utilization, and NSP cycles hang off the same record

The record the whole platform reasons about

Because that one device record is what the schedule, utilization, and NSP cycles all hang off, a device's status and its evaluation window never drift into two different places. When a scheduler or the director of training opens a device, they see the same record the rest of the platform reasons about — bookings, utilization, and the eval clock (for Part 60-qualified FFS/FTD) all reading from it.

Schedule, utilization, and NSP cycles hang off the same record
Status and eval window never live in two places

NSP evaluation cycles

14 CFR Part 60 · per-device · auto-rolling

Devices on NSP

Due ≤ 14d

Pass rate

100%

DeviceNext dueStatus

FFS-01 · B737-800in 11 daysDue soon

FFS-02 · A320in 84 daysOn track

FTD-04 · B737 FTDin 6 daysDue now

FFS-01 · last eval Satisfactory

Evaluator + organization · findings + corrective actions captured · next-due rolled forward

Reminders ahead of the deadline · pass rate on the Reports page

How an operator uses this

Every training device — a Full Flight Simulator from Level A through D, an FTD, an AATD, or a BATD — is a single record carrying its current operational status. FFS and FTD carry a genuine Part 60 qualification level; AATD and BATD are approved through a separate Letter of Authorization (LOA) under 61.4(c) rather than a Part 60 level, and the same record tracks that distinction instead of lumping every device type under one "qualification level." Because that one record is what the schedule, utilization, and NSP cycles all hang off, a device's status and its evaluation window never drift into two different places. When a scheduler or the director of training opens a device, what they see is the same record the rest of the platform reasons about.

Illustrative — every screen reflects what's in your own data, nothing more.

How it works

Device inventory, step by step

Add each device once, recording its type (FFS Level A–D, FTD, AATD, or BATD) and — for FFS/FTD — its Part 60 qualification level, or — for AATD/BATD — its LOA.
Set the device's operational status so the floor and the schedule reflect whether it's available.
Book sessions, track utilization, and run NSP cycles directly against that same device record.
Open any device to see its qualification level (or LOA, for AATD/BATD) and status in one place — never a wall list and a spreadsheet that disagree.

Questions

Device inventory — frequently asked

Which simulator types can I track?

Full Flight Simulators across Level A–D, plus FTD, AATD, and BATD devices. FFS and FTD carry a Part 60 qualification level; AATD and BATD are approved via a separate Letter of Authorization (LOA) under 61.4(c), not a Part 60 level — each device is one record carrying whichever applies, plus its operational status.

Where do scheduling and NSP cycles get a device's details?

From the same device record. The schedule, utilization, and NSP cycles all hang off it, so a device's status and its evaluation window never live in two different places. (NSP applies to Part 60-qualified FFS/FTD; AATD/BATD are tracked by their LOA instead.)

Keep exploring