IAD05LA130 · Cessna 172S
American Flight Services Cessna 172S · Accident: partial loss of engine power (mechanical failure) en route
From Reading Regional Airport (Carl A Spaatz Field) (RDG) to Reading Regional Airport (Carl A Spaatz Field) (RDG)
Event
- NTSB case
- IAD05LA130
- 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 172S
- 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
- N972SP
- Operator
- American Flight Services
- Onboard fatalities
- Unknown
- Route
- From Reading Regional Airport (Carl A Spaatz Field) (RDG), Reading, PATo Reading Regional Airport (Carl A Spaatz Field) (RDG)
- 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
- Partial loss of engine power (mechanical failure)
- 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 › Proper touchdown point, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While in cruise flight, the airplane's engine lost partial power and began to "run rough." The pilot elected to fly the airplane to a nearby airport. Because he was concerned that the engine might stop producing power, the pilot flew a higher than normal traffic pattern, landed with excessive speed, and subsequently overran the runway. The airplane then impacted a utility pole and a tree, resulting in substantial damage. Examination of the engine revealed that the number two cylinder exhaust valve had seized, which resulted in the partial loss of engine power.
Probable cause
The pilot's failure to attain a proper touchdown point as a result of the airplane's excessive airspeed. A factor was the partial loss of engine power due to a seized exhaust valve.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD05LA130
- Event ID
- 20050913X01438
- Case number
- IAD05LA130
- 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: 9d4601120b50dfd1e69a30f92a7808ed4c87609bf543c783d83300e791d9cda8; retrieved 2026-09-22T05:24:50.334Z.