Hunt Air Couriers Cessna T210M accident
Cessna T210M · Accident: total loss of engine power (non-mechanical) on approach
From Hector International Airport (FAR) to Springdale Municipal Airport (ASG)
Event
- NTSB case
- CHI93LA287
- 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
- Charter & commuter
- 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 T210M
- 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
- N761DD
- Operator
- Hunt Air Couriers
- Onboard fatalities
- Unknown
- Route
- From Hector International Airport (FAR), Fargo, NDTo Springdale Municipal Airport (ASG), Springdale, AR
- 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 135: Air Taxi & Commuter
- 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 pattern final
- 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; Wire, transmission
- 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, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITH LOWER THAN EXPECTED FUEL GAUGE READINGS, THE PILOT DECIDED TO LAND AT NEOSHO TO CHECK THE FUEL QUANTITY. UNABLE TO ACTIVATE THE RUNWAY LIGHTS, THE PILOT WAS ON FINAL APPROACH TO LAND WITHOUT LIGHTS, WHEN HE IMPACTED POWER LINES AFTER LOSING TOTAL ENGINE POWER. THE AIRCRAFT PROCEEDED TO IMPACT TWO TREES AND A BARBED WIRE FENCE. FURTHER INVESTIGATION FOUND LESS THAN 1/2 QUART OF TOTAL FUEL IN THE FUEL SYSTEM AND TANKS.
Probable cause
IS THE PILOT IN COMMAND'S FAILURE TO MAINTAIN PROPER CLEARANCE. FACTORS RELATING TO THIS ACCIDENT ARE THE PILOT IN COMMAND'S INADEQUATE PREFLIGHT PREPARATION AND THE LOSS OF TOTAL ENGINE POWER AS A RESULT OF FUEL EXHAUSTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA287
- Event ID
- 20001211X12867
- Case number
- CHI93LA287
- 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: f58a120d9cdbeaf05318d9893b629e9510f3b0d15cc4b9efd8c369d6a9941df2; retrieved 2026-09-18T18:32:16.280Z.