BFO93LA074 · Cessna 172
Cessna 172 · Accident: airframe, component or system failure during initial climb
From N27 to Skyhaven Airport (76N)
Event
- NTSB case
- BFO93LA074
- 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 172
- 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
- N3914F
- Operator
- Glenn E. Murphy · private individual
- Onboard fatalities
- Unknown
- Route
- From N27To Skyhaven Airport (76N), Tunkhannock, 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
- Initial climb
- 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
- Destroyed
Cause areas
- Flt control syst, aileron control cable/rod › Corroded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF, THE LEFT AILERON CONTROL CABLE FAILED IN THE VICINITY OF THE RIGHT AFT DOOR POST IN THE LOCATION OF A PULLEY. THE PILOT STATED IT TOOK FULL RIGHT AILERON TO KEEP THE AIRPLANE FROM ROLLING. THE AIRPLANE REMAINED IN THE TRAFFIC PATTERN TO LAND. DURING THE BASE LEG, THE PILOT APPLIED FULL FLAPS. THE AIRPLANE CONTINUED TO ROLL LEFT AND THE AILERONS DID NOT RESPOND TO CONTROL INPUTS. THE AIRPLANE IMPACTED THE GROUND LEFT WING DOWN AND CAME TO REST INVERTED. A METALLURGICAL EXAMINATION OF THE FAILED CABLE REVEALED THAT IT WAS CORRODED IN THE AREA OF THE FAILURE. THE AIRPLANE HAD RECEIVED A 100 HOUR ANNUAL INSPECTION ON OCTOBER 3, 1992. SINCE THE INSPECTION, THE AIRPLANE HAD FLOWN ABOUT ONE HOUR. THE AIRPLANE WAS TIED DOWN OUTSIDE FOR MOST OF THE TIME SINCE PURCHASED IN THE YEAR 1958. THE FAILED AILERON CONTROL CABLE WAS AN ORIGINAL CABLE.
Probable cause
THE FAILURE OF THE AILERON CONTROL CABLE WHICH RESULTED IN LOSS OF CONTROL IN FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA074
- Event ID
- 20001211X12305
- Case number
- BFO93LA074
- 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: bd11688aec43946187f068990cfe3be63bdfce5c3526d2ba0cf856ff4fec4e91; retrieved 2026-09-21T14:25:54.193Z.