# NTSB ERA09CA541: Cessna 172P, N55437, Pensacola, FL, September 27, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 27, 2009, 07:40 local (12:40 UTC)
- Place: Pensacola, FL
- Coordinates: 30.473333, -87.186386 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=30.4733&lon=-87.1864&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report March 3, 2010
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 74823
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA541
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74823/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74823
- Page: https://openairdocs.org/ntsb/ERA09CA541

## Probable cause

The pilot's inability to maintain control during landing due to the separation of the nose landing gear upper scissor from the nose gear assembly. Contributing to the accident was the inadequate visual examination performed during the annual inspection.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Landing gear system: landing gear steering system](https://openairdocs.org/ntsb-findings/01023250): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Cessna 172P, 1 case](https://openairdocs.org/ntsb-findings/01023250/cases.md?model=2072436), [All aircraft, 32 cases](https://openairdocs.org/ntsb-findings/01023250/cases.md)
- [Maintenance/inspections: scheduled maint checks](https://openairdocs.org/ntsb-findings/01010520): Aircraft › Aircraft handling/service · Inadequate inspection (probable cause); cases with it: [Cessna 172P, 1 case](https://openairdocs.org/ntsb-findings/01010520/cases.md?model=2072436), [All aircraft, 76 cases](https://openairdocs.org/ntsb-findings/01010520/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-events/330/sequence.md?model=2072436), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md)
- [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172P, 37 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072436), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172P, 29 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072436), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172P, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072436), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The student pilot stated that he was performing touch-and-go landings prior to the accident. Shortly after his third landing, the airplane veered left and impacted a taxiway sign. The nose landing gear separated from the airframe and resulted in substantial damage to the firewall. Examination of the airplane's nose landing gear by a Federal Aviation Administration inspector revealed that the upper scissor bolt, cotter pin, and castle nut were missing. Winding tire marks were observed on the runway prior to the airplane veering off the runway. Examination of the airplane found no damage to the nose landing gear scissor flange or nose landing gear scissor. In addition, the upper scissor flange bolt was not recovered, nor was any evidence identified that indicated the bolt was in place at the time of separation. An annual inspection was performed 17 days prior to the accident flight. A visual examination of the nose landing gear was performed, but no maintenance was required to be performed. The airplane accumulated 18 hours of flight time after the annual inspection prior to the accident.

## Factual narrative

The student pilot stated that he was performing touch and go landings prior to the accident. Shortly after his third landing, the airplane veered left and impacted a taxiway sign. The nose landing gear separated from the airframe and resulted in substantial damage to the firewall. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the upper scissor bolt, cotter pin, and castle nut were missing. Winding tire marks were observed on the runway prior to the airplane veering off the runway. Examination of the airplane by an airframe and power plant (A&P) mechanic found no damage to the nose landing gear scissor flange, or nose landing gear scissor. In addition, the upper scissor flange bolt was not recovered, nor was any evidence identified that indicated the bolt was in place at the time of separation. An annual inspection was performed 17 days prior to the accident flight. A visual examination of the nose landing gear was performed, but no maintenance was required to be performed. The airplane accumulated 18 hours of flight time after the annual inspection prior to the accident.

## Aircraft

- Registration: [N55437](https://openairdocs.org/deregistered/N55437-2018-01-25), registration cancelled 2018-01-25, S/N 17275180, built 1981 (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17275180
- Airframe hours: 6996
- Engines: LYCOMING 0-320 SERIES 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Pensacola Navy Flying Club Inc
- Registered owner: Pensacola Navy Flying Club Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, September 10, 2009, 18 hours before
- Departed: PNS, Pensacola, FL
- Destination: PNS, Pensacola, FL
- Flight plan: Unknown
- Airport: PNS, Pensacola Regional Airport, runway 35, 7,004 × 150 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 39; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 15 total, 15 in this make and model, 3 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 330° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 73 °F, dew point 72 °F
- Altimeter: 29.93 inHg
- Observed at: PNS

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20090927050229A](https://openairdocs.org/incident/20090927050229A), Sep 27, 2009: Cessna 172P, Pensacola, FL, Substantial damage. On September 27, 2009 under VMC conditions at approximately 0735 hrs a Cessna 172P with a student pilot at the controls was performing touch and go's on runway…

## Docket (5 files)

The files NTSB released with the investigation on November 6, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74823. 982 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 834 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320419&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Memorandum for Record (FAA inspector) (item 2, .PDF, 26 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320420&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20(FAA%20inspector)-Master.PDF
- Photo 1: Digital picture provided by FAA inspector showing separated nose landing gear with intact scissor and scissor flange. (item 3, .PDF, 55 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320422&FileExtension=.PDF&FileName=Photo%201%3A%20Digital%20picture%20provided%20by%20FAA%20inspector%20showing%20separated%20nose%20landing%20gear%20with%20intact%20scissor%20and%20scissor%20flange.-Master.PDF
- Cessna 172 Nose Landing Gear Parts Catalog (item 4, .PDF, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320425&FileExtension=.PDF&FileName=Cessna%20172%20Nose%20Landing%20Gear%20Parts%20Catalog-Master.PDF
- Memorandum for Record (A&P mechanic) (item 5, .PDF, 27 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40320521&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20(A%26P%20mechanic)-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
