CEN24LA206 · Piper PA-24-250
Piper PA-24-250 · Accident: fuel related on approach
From Denton Enterprise Airport (DTO) to an unrecorded destination
Event
- NTSB case
- CEN24LA206
- 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
- Event fatalities
- Unknown
- 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
Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N7500P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Denton Enterprise Airport (DTO), Denton, TXTo not recorded
- Aircraft age
- About 63 years (built 1961)
- 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
- Approach · VFR pattern downwind
- Defining eventThe 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
- Fuel related
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that after a cross-country flight at 10,500 ft mean sea level (msl), he had descended and was approaching to land. When the airplane was abeam the runway numbers on the downwind leg of the traffic pattern, about 7,500 ft msl, he noticed that the engine sounded as if it was no longer producing power. He attempted to restore power but was not successful and executed a forced landing to a field which resulted in substantial damage to the fuselage and right wing. Postaccident examination revealed no preimpact anomalies that would have precluded normal operation. First responders stated that the airplane’s wing contained fuel, the fuel selector was positioned for the left main fuel tank, and that the left fuel gauge read just over ½ tank of fuel remaining. The recovery company confirmed the presence of fuel in the airplane but could not provide a detailed report of how much fuel each fuel tank contained. The pilot reported in a telephone interview that he did not use carburetor heat at any time during the accident flight or during troubleshooting procedures. When he was about 20 minutes from his destination, he descended to about 9,000 ft. msl, and switched to the fullest fuel tank. He also adjusted settings as appropriate for the approach. When in the traffic pattern, once he realized that the engine had lost power, he said attempted to restore engine power using the emergency procedures from the pilot’s operating handbook (POH), including switching fuel tanks, and activating the airplane’s electric fuel boost pump. When engine power was not restored, he switched back to the previous tank as it should have contained the most fuel. Review of the POH revealed that the normal approach and landing procedures state: “Carburetor heat should not be applied unless there is an indication of carburetor icing, since the use of carburetor heat causes a loss in engine power which may be critical in the event of a go-around, and can induce detonation in this situation.”
The POH stated in the “Emergency Procedures” section that in the event of an engine failure the first step would be to switch fuel tanks, and if this did not restore engine power the pilot should:
Check fuel pressure and turn on electric fuel pump, if off. Push Mixture control to full rich. Apply carburetor heat. Check ignition switch. The temperature and dewpoint at the accident airport were conducive to serious icing at glide power settings. Given the lack of mechanical anomalies found and the recorded temperature and dewpoint being within a range conducive for carburetor icing, the likely reason for the loss of engine power was due to carburetor icing.
Probable cause
The pilot’s failure to use the carburetor heat during a descent that resulted in the loss of engine power due to carburetor icing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA206
- Event ID
- 20240603194365
- Case number
- CEN24LA206
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: e8f36ad28aa3ffc04e231f60d247c9608a822d479003adb3359627e7d95101ed; retrieved 2026-09-16T18:49:50.804Z.