FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25LA127 · Cessna 172 P

22 Feb 2025 · Mayo, MD, United States

Cessna 172 P · Accident: fuel related en route

From Delaware Airpark (33N) to Fort Meade Executive Airport (FME)

Report a problem

Event

NTSB case
ERA25LA127
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 172 P

Aircraft type
Cessna 172
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
N781FM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Delaware Airpark (33N), Dover, DETo Fort Meade Executive Airport (FME), Odenton, MD
Aircraft age
About 45 years (built 1980)
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 · descent
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

During a solo cross-country flight, the student pilot initiated a cruise-power descent from about 2,300 ft and about 2300 rpm (about 65% engine power). He reported that, when the airplane was about 1,500 ft, it felt like the engine was “pulled to idle.” He stated that he manipulated the throttle control, but the engine did not respond. He confirmed that the mixture control was set to full rich, the fuel selector was in the Both position, and the primer was locked. He said he then applied carburetor heat, which had “no effect,” then he removed carburetor heat and looked for a place to land the airplane. The student pilot selected a road for a forced landing, and the airplane’s right wing impacted trees about 10 ft above the surface and the airplane continued striking trees after ground contact. The airplane came to rest upright on its nose against trees on the side of a two-lane road. An odor of fuel was present at the site, but the contents of the fuel tanks could not be established due to the airplane’s position. Examination of the airframe and engine found no abnormality that would have prevented normal operation. A serviceable propeller was installed, and an engine start was initiated on a test stand. The engine started immediately, then idled, accelerated, and ran smoothly at full power for several minutes without interruption and no anomaly noted. A magneto check was performed with no anomaly noted, and oil indicated pressures were in the normal range. Engine power was reduced to idle, where the engine ran smoothly without interruption. A magneto grounding check was normal, and a slight rpm rise was heard when the mixture was pulled to idle cutoff. The engine was stopped with the mixture placed at the idle cutoff position. A post-run inspection of the engine revealed no leaks and no abnormality. The atmospheric conditions near the accident site around the time of the accident were conducive to the formation of carburetor icing at glide and cruise power settings. Given the atmospheric conditions and the lack of mechanical anomalies found during postaccident examination and an engine test run, the engine likely lost power due to the accumulation of carburetor icing during the en route descent. Although the student pilot’s subsequent brief (rather than sustained) application of carburetor heat was inconsistent with the emergency procedures for responding to a loss of engine power, this likely did not affect the outcome of the flight. Given the airplane’s low altitude when the student first perceived the engine power anomaly, it is unlikely that carburetor heat applied in response could have cleared the ice and restored engine power in time to prevent the forced landing.

Probable cause

A total loss of engine power at low altitude due to an accumulation of carburetor ice while in a cruise-power descent, which resulted in a forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA25LA127
Event ID
20250225199758
Case number
ERA25LA127
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: faff1178c0a26d9fa59f2a7a3a17493e2a3dd4871559ad5e2cfef14f36c12c47; retrieved 2026-09-16T19:41:35.301Z.