Flight Simulator Training in Flight Schools: What BATDs and AATDs Actually Buy You Under Parts 61 and 141

A cold front moves across the field on a Friday afternoon. The pattern goes to 800 broken and three miles, gust factor pushes crosswind past school limits on the training runway, and the dispatcher looks at four instrument students booked between now and 1900 local. In a fleet-only school the afternoon becomes four cancellations, four instructor no-pay hours, and four students who will finish the syllabus later than the plan said. In a school that owns an approved simulator and knows what to do with it, three of those four lessons still happen, three instructors still get paid, and the students walk out with the approach they were supposed to fly logged and signed.

The device in the corner of the classroom is not a toy. Under Parts 61 and 141 it is a specific class of ground trainer with specific time credit, specific approval limits, and a specific place in the syllabus. The schools that treat it that way are the schools whose weather days do not compound into schedule debt the CFI pool cannot dig out of.

What the FAA Actually Calls These Devices

Three acronyms carry most of the confusion. A Basic Aviation Training Device (BATD) is an FAA-approved ground trainer meeting the standards in AC 61-136B, typically a desktop station with a single yoke or stick, a throttle quadrant, an avionics stack, and an instrument panel display. An Advanced Aviation Training Device (AATD) is the next tier: a higher-fidelity setup with a more accurate flight model, tighter switch fidelity, and often an enclosed cockpit shell. A Flight Training Device (FTD) is a separate FAA classification, closer to a full-motion simulator, and priced past what most Part 61 or small Part 141 schools operate.

For most training operations, BATD and AATD are the two that matter, and the difference between them shows up in the maximum time credit the FAA will let the student log.

What Part 61 Actually Credits

The credit structure lives in 14 CFR 61.51(g) and 61.65. A student working toward a private pilot certificate can log time from an FAA-approved BATD or AATD, but the credit does not substitute for airplane time in the certificate requirements. The instrument rating is where the numbers get interesting. Under 14 CFR 61.65(i), a student may credit up to ten hours of BATD time toward the forty-hour instrument-time requirement, and up to twenty hours of AATD time. That is the difference between owning a BATD and owning an AATD in practical terms: on an instrument syllabus, the AATD absorbs twice as much of the required time.

Simulator time also counts toward instrument currency under 14 CFR 61.57(c). It counts toward the sixty-six-day approaches, holds, and course-intercept tasks a rated pilot needs to remain legal to file IFR. That currency credit is where a school's own CFIs use the device on the schedule they set for themselves, and where the trainer earns keep across the school and not just against student syllabi. The instrument proficiency check can also be conducted in an approved BATD or AATD under the same paragraph, subject to instructor and evaluator restrictions.

Part 141 Draws the Lines Differently

A Part 141 school runs against a training course outline approved by the FSDO, and the simulator credit lives in that document. Part 141 Appendix C for the private course, Appendix D for the instrument course, and the equivalent appendices for commercial and CFI courses each set a maximum percentage of the course that can be conducted in an FAA-approved training device. The instrument course allows up to fifty percent of the flight training in an approved device, which is a significantly larger share than the ten or twenty hours a Part 61 student can credit against the forty-hour requirement.

The tradeoff is that the credit is only as good as the training course outline the FSDO signed. A school that added a new BATD after the outline was approved does not automatically get to log against it. The amendment has to be filed and accepted first. The Part 61 versus Part 141 distinction matters here for the same reason it matters everywhere else: the structure the school chose determines what the device can carry.

Where the Simulator Earns Its Keep on the Schedule

The obvious answer is weather. A device that flies in 800 broken with a gust factor is a device that recovers the day the airplanes cannot. The less obvious answer is procedure fluency. A student learning the ILS at the home field for the first time in the airplane is paying tach time and instructor time to build muscle memory that would have cost a quarter as much on the ground. The schools that treat the BATD as a procedure trainer for approach setup, missed approach initiation, holding entries, DME arcs, and unusual attitudes at instrument speeds are the schools whose airplane hours produce checkride-ready students without doubling the hobbs meter.

The device also solves the scenario problem. A partial-panel failure in cruise, a vacuum pump loss on approach, or a comm failure in Class Charlie are training events a CFI cannot manufacture in an airplane without either telegraphing the failure or losing altitude the CFI would rather not lose. On the ground trainer the failure is a keystroke and the debrief is honest.

Treat the Simulator Like an Aircraft on the Schedule

Time in a BATD or AATD is time the student pays for and the instructor is paid for. It has to live on the same booking calendar the airplanes do, be released against the same dispatch rules, and be billed against the same run-time or lesson-block clock the Hobbs-versus-tach discussion already sorted out for the fleet. A device that lives in a room the front desk cannot see is a device that gets scheduled by whoever remembered it existed, which is usually nobody.

The clean pattern is the one that runs through good fleet management: the trainer is a resource on the schedule, has an instructor assigned like an airplane does, and closes with an entry in the logbook the same day the lesson ends. A school whose CFIs endorse simulator time in a stack of paperwork the following Tuesday is a school whose records will not survive a records request from a DPE prepping a candidate.

What the Simulator Does Not Buy You

Simulator time does not build the physical stick-and-rudder that keeps a student on centerline in a fifteen-knot direct crosswind. It does not develop the situational scan a pilot uses to sequence a busy Class Delta pattern. It does not substitute for the solo experience the certificate requires and the FAA counts separately. A school that lets a BATD absorb too much of the airplane syllabus produces a student who passes the oral, briefs an approach cleanly, and struggles the first time the actual airplane behaves like an airplane in the actual weather.

The right ratio depends on the rating and the student, but the trend the CFIs at the school see over time is the honest test. A private pilot candidate who cannot land the airplane consistently after fifty hours has probably spent time in the wrong classroom, and no BATD hour recovers that.

The Device in the Corner Is a Business Line

A BATD amortized over three years pays for itself the first time it turns eight cancellations into eight lessons on a bad-weather Saturday. An AATD costs more and buys more Part 61 time credit and more of a Part 141 course. Either one, treated like an airplane and scheduled like an airplane, is a piece of the training infrastructure the school can plan against instead of a piece of hardware that shows up in inventory. The schools that never quite get the utilization right are the schools whose device sits in the corner and whose airplanes fly whatever weather the airplanes can survive.