ERA23LA074 · Textron Aviation Inc 172 S
Flyt Aviation Textron Aviation Inc 172 S · Accident: landing area undershoot
From Peachtree City Falcon Field (FFC) to an unrecorded destination
Event
- NTSB case
- ERA23LA074
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Textron Aviation Inc 172 S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N407MD
- Operator
- Flyt Aviation
- Onboard fatalities
- Unknown
- Route
- From Peachtree City Falcon Field (FFC), Atlanta, GATo not recorded
- Aircraft age
- About 1 year (built 2021)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area undershoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that while on a downwind leg of the airport traffic pattern, abeam the runway numbers, he simulated an engine failure for the student pilot. The student pilot performed checklist items, but the airplane was getting too low and far from the runway. The flight instructor then told him to turn directly toward the runway, which he did. The student pilot stated that he wanted to go-around, but the flight instructor said to keep going. By the time the flight instructor realized the airplane was not going to reach the runway threshold, he increased power, but the tail struck a runway light. The airplane subsequently landed uneventfully. The flight instructor stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. Postaccident examination of the airplane confirmed that the empennage had been substantially damaged.
Probable cause
The flight instructor’s inadequate remedial action during a simulated engine failure and low approach, which resulted in a collision with a runway light.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA074
- Event ID
- 20221129106379
- Case number
- ERA23LA074
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2f8d24eb713776fd69f6c2b4edd041bbf4c5e3537cbb42cb69e545fa41bd9bb4; retrieved 2026-09-16T16:29:35.861Z.