MKC88LA091 · Cessna 170B
Cessna 170B · Accident: airframe, component or system failure en route
From Four Corners Regional Airport (FMN) to ISN · Williston, ND
Event
- NTSB case
- MKC88LA091
- 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 170B
- Aircraft type
- Cessna 170
- 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
- N4510C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Four Corners Regional Airport (FMN), Farmington, NMTo ISN · Williston, ND
- 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
- Airframe, component or system failure
- 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 › Clearance, misjudged
- Pilot in command › Judgment, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT HE STARTED THE TRIP, FROM NEW MEXICO TO NORTH DAKOTA, THE EVENING PRIOR TO THE ACCIDENT. BECAUSE OF POOR WEATHER, THE PILOT RE-ROUTED THE FLIGHT THROUGH SEVERAL ALTERNATE FUEL AND OIL STOPS. THE FLIGHT WAS EN ROUTE TO A PLANNED FUEL STOP WHEN THE ENGINE LOST OIL PRESSURE. THE AIRCRAFT WAS TOO FAR FROM A SUITABLE AIRPORT AND THE PILOT WAS FORCED TO LAND ON A HIGHWAY. THE PILOT SECURED A RIDE TO THE NEAREST TOWN AND PURCHASED OIL. AFTER ADDING OIL TO THE AIRCRAFT'S ENGINE HE ATTEMPTED A TAKEOFF FROM THE HIGHWAY--AFTER GOING WITHOUT SLEEP FOR ALMOST 30 HOURS. DURING THE TAKEOFF ROLL, THE AIRPLANE STRUCK A SPEED LIMIT SIGN ON THE EDGE OF THE HIGHWAY WITH ITS RIGHT WING. THE PILOT THEN LOST DIRECTIONAL CONTROL AND THE AIRCRAFT SWERVED INTO A DITCH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC88LA091
- Event ID
- 20001213X25779
- Case number
- MKC88LA091
- 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: 469fb50fe024ae5d7ca2bc431f2971f59bc7e697f5e6e2ec085856b946c22417; retrieved 2026-09-23T10:16:04.723Z.