LAX84LA209 · Cessna TU-206G
Cessna TU-206G · Accident: loss of control in flight on approach
From Auburn Municipal Airport (AUN) to an unrecorded destination
Event
- NTSB case
- LAX84LA209
- 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
- 0
- 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 TU-206G
- Aircraft type
- Cessna TU-206
- 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
- N206GA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Auburn Municipal Airport (AUN), Auburn, CATo 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
- Loss of control in flight
- 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
- Stall
- 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 › Directional control, inadequate
- Pilot in command › Elevator trim, excessive
- Pilot in command › Flare, misjudged
- Pilot in command › Habit interference
- Pilot in command › Procedures/directives, poor
- Pilot in command › Raising of flaps, improper
- Pilot in command › Stall, not corrected
- Pilot in command › Throttle/power control, improper use of
- Pilot in command › Total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT CAME IN FOR HER 3RD LANDING AND AFTER FLARING HIGH'CUT'THE THROTTLE AND SAID SHE HOPED FOR A'SOFT'LANDING WITH TRIM BACK AND 40 DEGREES OF FLAPS. A PLT ON THE GROUND NEAR THE RWY SAID HIS ATTENTION WAS DRAWN TO THE ACFT BECAUSE OF A LARGE INCREASE IN ENGINE NOISE. HE SAID THE ACFT NOSE WAS HIGH,AIRSPEED SLOW AND THE ACFT APPEARED TO ENTER A'TORQUE ROLL'. HE ADDED IT POSSIBLY ROLLED DUE TO'P'FACTOR. THE LEFT WING HIT THE GROUND FIRST AND THE ACFT CAME TO REST ABOUT 200 FT OFF THE RWY. THE PLT SAID SHE MAY HAVE RAISED THE FLAPS TO GO AROUND BEFORE ADDING POWER. SHE ALSO SAID SHE MAY NOT HAVE USED ENOUGH RUDDER TO CORRECT FOR THE ADDED POWER. HER INSTRUCTOR SAID SHE TENDED TO USE TRIM INSTEAD OF RUDDERBUT HE THOUGHT SHE WAS'CURED'OF HER HABIT OF RAISING FLAPS BEFORE POWER BUT A'REFLEX SITUATION'MAY HAVE MADE HER HAVE THE PREDOMINANT IMPROPER REFLEX ACTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84LA209
- Event ID
- 20001214X39061
- Case number
- LAX84LA209
- 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. 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: 517a78c52432d9e96668c66b62fda3ca5b1a40d533847015b1604285a7dd8ec7; retrieved 2026-09-23T20:46:25.984Z.