SEA83FYM06 · Cessna T210L
Boeing Military Airplane Cessna T210L · Accident: total loss of engine power (non-mechanical) en route
From 0R33 · Boardman, OR to S22 · Hermiston, OR
Event
- NTSB case
- SEA83FYM06
- 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 T210L
- Aircraft type
- Cessna 210
- 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
- N393AC
- Operator
- Boeing Military Airplane
- Onboard fatalities
- Unknown
- Route
- From 0R33 · Boardman, ORTo S22 · Hermiston, OR
- 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, not maintained
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT STALLED INTO THE GROUND IN A SEMI-CONTROLLED CRASH FORCED LANDING AFTER THE ENGINE QUIT DUE TO FUEL EXHAUSTION.A POST ACCIDENT EXAMINATION REVEALED ONLY ONE OUNCE OF FUEL ABOARD THE ACFT. THE ACFT RELEASE FORM FROM BOEING AIRCRAFT TO THE PILOT FOR THE FLT SHOWED 75 GALLONS OF FUEL ON BOARD BEFORE RELEASE. SINCE THAT RELEASE THE ACFT HAD FLOWN 3 FLTSFOR A TOTAL OF 4:44 HOURS. THIS DOES NOT CONSIDER GROUND OPERATION. THIS AVERAGES OUT TO 15.8 GALLONS PER HOUR. THE MANUAL SHOWS 15 GALLONS PER HOUR FOR CRUISE AT 75 PERCENT POWER. THE TWO OCCUPANTS DURING THE CRASH LANDING DID NOT USE THEIR SHOULDER HARNESS AND BOTH RECEIVED SERIOUS INJURIES.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA83FYM06
- Event ID
- 20001214X43532
- Case number
- SEA83FYM06
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-06-08.
- API snapshot SHA-256: 4757981285ce61b083ea922a8d5435b93685a0f0d9fd777533db8fd499c4f27d; retrieved 2026-09-21T17:55:26.041Z.