NYC99LA153 · Cessna 182Q
Cessna 182Q · Accident: total loss of engine power (mechanical failure) en route
From Linden Airport (LDJ) to Montgomery County Airpark (GAI)
Event
- NTSB case
- NYC99LA153
- 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
- Instrument Meteorological Cond
Cessna 182Q
- Aircraft type
- Cessna 182
- 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
- N937FB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Linden Airport (LDJ), Linden, NJTo Montgomery County Airpark (GAI), Gaithersburg, MD
- 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 (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
- Destroyed
Cause areas
- Engine assembly, connecting rod bolt › Failure
- Powerplant › Overtemperature
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was in level flight at 4,000 feet, on a dark night, in instrument conditions, when the engine lost all power. The pilot performed a forced landing to a river. When the engine was examined, two holes were observed on the top of the engine crankcase. The heads of three connecting rod bolts and portions of a connecting rod bearing were recovered from the bottom of the oil sump pan. All of the main bearings, with the exception of the number four and five main bearings, exhibited accelerated wear and were blackened from heat stress. The number four and five cylinder connecting rod end caps and five connecting rod bolts were forwarded to the Safety Board Materials Lab. All five of the bolts exhibited severe necking at the fracture and deformation in the shafts. The large amount of deformation and necking was consistent with a single deformation event that occurred at a high temperature. The connecting rod caps exhibited similar characteristics, a gross amount of deformation, but with a lack of fracture. This was consistent with deformation at a high temperature. The engine had bee remanufactured about 9 years and 941 hours prior to the accident.
Probable cause
The failure of the connecting rod end bolts, due to an overtemperature condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99LA153
- Event ID
- 20001212X19103
- Case number
- NYC99LA153
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-06-21.
- API snapshot SHA-256: ec47108f683eb7118535d1d85693c75bd4858f55f5824f81d31b9f47d7c3c304; retrieved 2026-09-21T10:58:43.030Z.