DFW08LA019 · Cessna U206G
Cessna U206G · Accident: loss of engine power en route
From Ticonderoga Municipal Airport (4B6) to Sanford Seacoast Regional Airport (SFM)
Event
- NTSB case
- DFW08LA019
- 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 U206G
- 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
- N8777Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ticonderoga Municipal Airport (4B6), Ticoderoga, NYTo Sanford Seacoast Regional Airport (SFM), Sanford, ME
- 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
- En route · cruise
- 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 engine power
- 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
- Engine assembly, crankshaft › Fractured
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While en route to his destination the private pilot began experiencing a rough running engine with a subsequent total loss of engine power. Unable to make the nearest airfield the pilot elected to land in a farm field. During landing roll the nosewheel contacted a burrow resulting in the separation of the nosewheel assembly and a loss of control. The airplane came to rest in the upright position and the pilot was able to egress without assistance. During the engine examination a sub-surface fatigue fracture was discovered on the number 5 crankshaft cheek resulting in the failure of the crankshaft and loss of engine power. The engine was last overhauled approximately 17 years prior to the accident. The engine manufacturer stated that the engine should be overhauled every 12 years. On January 23, 1998, the Federal Aviation Administration released guidance for the replacement of the crankshaft at the next overhaul or the next time the crankshaft was removed. At the time of the accident, compliance with the service bulletin and airworthiness was not accomplished, nor required.
Probable cause
Failure of the crankshaft resulting in the total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08LA019
- Event ID
- 20071025X01657
- Case number
- DFW08LA019
- 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: fb5b891bc5d5f079425100369784829f79953cc4ee1a664c6e2a96a6c13fbdeb; retrieved 2026-09-22T03:20:09.075Z.