NYC90LA080 · Cessna CE-172P
Cessna CE-172P · Accident: loss of engine power en route
From Lawrence Municipal Airport (LWM) to John Murtha Johnstown Cambria County Airport (JST)
Event
- NTSB case
- NYC90LA080
- 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 CE-172P
- Aircraft type
- Cessna CE-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
- N62274
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lawrence Municipal Airport (LWM), Lawrence, MATo John Murtha Johnstown Cambria County Airport (JST), Johnstown, PA
- 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
- Loss of engine power
- 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
- Pilot in command › Fuel consumption calculations, inadequate
Approximate · Estimated position: the centre of Hollidaysburg, PA, the place the record names. Not the accident site.
NTSB narrative
THE PILOT RECEIVED A PREFLIGHT WEATHER BRIEFING PRIOR TO TAKEOFF AND USING THE WINDS ALOFT HE CALCULATED HOW LONG THE FLIGHT WOULD TAKE TO ARRIVE AT HIS DESTINATION AND HOW MUCH FUEL WOULD BE NEEDED. HE CHECKED THE TANKS VISUALLY. THE PILOT SAID WHEN ABOUT 15 MILES OUT FROM JOHNSTOWN, THE ENGINE BEGAN TO RUN ROUGH AND THEN IT QUIT. AN EMERGENCY LANDING WAS MADE IN A GRASS FIELD AND THE LEFT WING CONTACTED A TREE ROTATING THE AIRCRAFT ABOUT T 130 DEGREES TO THE LEFT. INSPECTION OF THE AIRCRAFT REVEALED NO FUEL IN THE TANKS AND THERE WERE NO LEAKS.
Probable cause
PILOT FACTOR IN THAT HE FAILED TO ENSURE THERE WAS SUFFICIENT FUEL ON BOARD TO COMPLETE THE FLIGHT. THIS RESULTED IN AN ENGINE FAILURE & SUBSEQUENT FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90LA080
- Event ID
- 20001212X22809
- Case number
- NYC90LA080
- 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: 1cdf01fcfe409963c11547d242397837ecea519d4357ace18b52de04b3bcc6c3; retrieved 2026-09-23T06:36:47.141Z.