IAD05IA066 · Cessna R182
Steel City Aviation Cessna R182 · Incident: airframe, component or system failure while maneuvering
From Allegheny County Airport (AGC) to Allegheny County Airport (AGC)
Event
- NTSB case
- IAD05IA066
- 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
- Incident
- 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 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
- N6149S
- Operator
- Steel City Aviation
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), West Mifflin, PATo Allegheny County Airport (AGC)
- 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
- Maneuvering
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Landing gear, gear locking mechanism › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering, the pilot moved the landing gear handle to the "down" position, and received an unsafe indication for the nose landing gear. He then attempted to troubleshoot the system and lower the landing gear manually, but without success. A normal landing was performed to the runway, and the airplane started to roll out on all three landing gear. While decelerating through approximately 40 knots, the nose gear collapsed, the propeller struck the runway, and the airplane slid to a stop on its nose. Examination of the nose landing gear revealed that a downlock actuator pin on the nose landing gear actuator had failed due to fatigue, and worked partially out of its clevis half. The broken pin contacted the actuator arm piston, and prevented the full travel of the nose landing gear to the down and locked position. A manufacturer's service bulletin that addressed the inspection and replacement of the downlock pins had not been completed.
Probable cause
The failure of the landing gear actuator downlock pin due to fatigue, which resulted in the nose landing gear collapsing on landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD05IA066
- Event ID
- 20050602X00713
- Case number
- IAD05IA066
- 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: 7662be34fe876e735b1e0bda1167adc02828bc8d5099f4e5b3a70b27c6fec7e1; retrieved 2026-09-22T05:54:45.641Z.