MIA01LA207 · Cessna 172N
Cessna 172N · Accident: in flight collision with object on approach
From DeKalb Peachtree Airport (PDK) to an unrecorded destination
Event
- NTSB case
- MIA01LA207
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
Cessna 172N
- 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
- N3467E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Atlanta, GATo not recorded
- Aircraft age
- Not recorded
- 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
- Approach · VFR go-around
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command(cfi) › Go-around, delayed
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The instructor and student stated that during a simulated engine out approach and landing, the approach was at a higher than normal glide path. Touch down was further down the runway than normal. The dual student stated it would have been possible to complete the landing roll in the grass, however, the instructor initiated a go-around. The dual student stated the stall warning horn activated during the climb and the airplane contacted trees at the departure end of the runway. The instructor stated they had no mechanical failures with the airplane. The engine was operated to full power after the accident with no evidence of failure or malfunction. The carburetor heat was found on after the accident.
Probable cause
The flight instructor's improper monitoring of the dual student during a simulated engine out approach and her delayed decision to initiate a go-around resulting in the airplane colliding with trees at the departure end of the runway during the go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA207
- Event ID
- 20010808X01631
- Case number
- MIA01LA207
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: aa15298aa82a2c873279784259e5026a861ded6d58d1281703a35eb4cdaa1741; retrieved 2026-09-21T19:52:59.540Z.