IAD05FA068 · Cessna R182
Cessna R182 · Accident: total loss of engine power (mechanical failure) en route
From Malone Dufort Airport (MAL) to Long Island MacArthur Airport (ISP)
Event
- NTSB case
- IAD05FA068
- 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
- 2 · 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 R182
- 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
- N756PN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Malone Dufort Airport (MAL), Malone, NYTo Long Island MacArthur Airport (ISP), Islip, NY
- 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)
- 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
- Tree(s)
- 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, bearing › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was in cruise flight, at 4,000 feet, when the engine lost oil pressure. The pilot reported the difficulty to air traffic control, was given vectors to an airport 10 miles to the south, and cleared for a descent. About 2 minutes after the pilot's initial call, he reported the engine had seized. Unable to reach the airport, the pilot attempted the forced landing in a sports field of relatively short length. The airplane glided low over the field, but continued beyond the end where it hit trees. The airplane then impacted the ground, and a postcrash fire ensued. A subsequent examination of the engine revealed that the aluminum-clad bearings from the number two connecting rod had failed, and that the rod beam and cap had separated.
Probable cause
Failure of the aluminum-clad, number two connecting rod bearings, which resulted in a total loss of engine power. A factor was the relatively short forced landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD05FA068
- Event ID
- 20050602X00708
- Case number
- IAD05FA068
- 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: b169f8576ca9dbcc5a8d70fb37ba44430b54afa6c8411dd25698f0165335c389; retrieved 2026-09-20T18:02:31.910Z.