CEN10CA378 · Cessna 206 UNDESIGNAT
Cessna 206 UNDESIGNAT · Accident: abnormal runway contact during landing
From Double Eagle II Airport (AEG) to Double Eagle II Airport (AEG)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10CA378
- 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 206 UNDESIGNAT Narrative disagrees
- Aircraft type
- Cessna 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
- N164SA
- Operator
- Berndt P Schmit · private individual
- Onboard fatalities
- Unknown
- Route
- From Double Eagle II Airport (AEG), Albuquerque, NMTo Double Eagle II Airport (AEG), Albuquerque, NM
- 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
- 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
- Abnormal runway contact
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was practicing touch and go and full stop landings. On the third landing attempt the pilot had about 25 degrees flaps selected because he recognized he was higher and closer to the runway than normal. He felt he was stabilized on final at about 85 knots by mid-final. He flared and touched down lightly, but the airplane bounced slightly and floated one to two feet above the runway. The pilot added back pressure and the airplane suddenly touched down. The pilot added power and a porpoise developed. The propeller struck the runway and the nose gear collapsed, bending the firewall. The airplane stopped on the runway. The pilot did not report any airplane malfunctions prior to the accident.
Probable cause
The pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA378
- Event ID
- 20100708X85312
- Case number
- CEN10CA378
- 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, 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: 404ae7c0c7645bfe6df0e176a5dd811ecb626c3416ff28bf1cec92c9fae2c2cd; retrieved 2026-09-15T14:40:10.694Z.