DFW06CA051 · Cessna 177
Cessna 177 · Accident: total loss of engine power (non-mechanical) en route
From Antlers Municipal Airport (80F) to Mc Alester Regional Airport (MLC)
Event
- NTSB case
- DFW06CA051
- 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 177
- Aircraft type
- Cessna 177
- 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
- N2233Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Antlers Municipal Airport (80F), Antlers, OKTo Mc Alester Regional Airport (MLC), MC ALESTER, OK
- 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)
- 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 › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 800-hour private pilot reported in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that he departed the airport with 6 gallons of fuel on-board enroute to another airport located approximately 40 miles away, where he was expecting to refuel his single-engine airplane. About 10 miles from the point of departure, while at a cruise altitude of 2,500 feet msl, the engine "coughed", and the pilot elected to turn back towards his departure airport. When the airplane was approximately 2 miles from the airport the engine lost power and the pilot elected to execute a forced landing to an open pasture parallel to the interstate highway. The pilot added that while on short final for the forced landing, the airplane encountered wind shear resulting in a hard landing. The winds at the time of the accident were reported from 300 degrees at 20 knots, gusting to 40 knots.
Probable cause
The loss of engine power due to fuel exhaustion as result of the pilot's inadequate preflight planning. A contributing factor was the encounter with windshear during the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA051
- Event ID
- 20060223X00227
- Case number
- DFW06CA051
- 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: 7ea0e734bde5ffd3aab8430d1a69103ee66064ca6c6363a77b76dfd81b164895; retrieved 2026-09-21T18:50:08.399Z.