# Accident 20130730014889A: Cessna 172S, Mesa, AZ, July 30, 2013

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 30, 2013, 11:30 local time
- Place: Mesa, AZ
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: Pilot school (Part 141)
- Operator: O00S
- Location: 33.4223° N, 111.8226° W: Placed by OpenAirDocs: center of Mesa, AZ, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.4223&lon=-111.8226&mi=10
- Aircraft: N635ND, registered now (https://openairdocs.org/aircraft/N635ND) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 0
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130730014889A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

N635ND IS OWNED AND USED AT A FLIGHT SCHOOL.

DURING A PREFLIGHT CHECK ON JULY 30, 2013, THE PILOT OBSERVED DAMAGE TO THE FIREWALL. THIS INSPECTION IS A REQUIRED PREFLIGHT CHECK PER THE UND CHECKLIST.

INVESTIGATION HAS DETERMINED THAT THE FAA IS UNABLE TO COMPLETELY DETERMINE WHO THE PILOT WAS THAT MAY HAVE CAUSED THE DAMAGE. THIS IS DUE TO THE FOLLOWING CONDITIONS:

THE PREFLIGHT AND POST FLIGHT FIREWALL 'INSPECT' IS REQUIRED IN THE UND CHECKLIST. THIS INSPECTION REQUIRES GOOD LIGHT VISIBILITY TO SEE DOWN THE COVER PLATE IN ORDER TO 'INSPECT' THE FIREWALL. THE POSITION OF THE AIRCRAFT TO THE SUN CAN HAVE AN IMPACT ON VISIBILITY AND NIGHT TIME IS NO GOOD WITHOUT A FLASHLIGHT.

THE PILOTS HAVE NO PRIOR EXPERIENCE IN ACTUAL RECORDING THE DIFFERENCE BETWEEN A PASSING AND A FAILING 'INSPECTION' OF THE FIREWALL.

THE AIRCRAFT IS BEING USED BY MULTIPLE PILOTS AND HAS BEEN USED OVER MANY FLIGHTS SINCE THE PREVIOUS MAINTENANCE INSPECTION PERFORMED BY THE OFFICE A&P.

THE LIKELY CAUSE OF THE ACCIDENT DAMAGE IS RESULTING FROM A LANDING OR TOUCH AND GO EXERCISE WHERE THE AIRCRAFT WAS BROUGHT DOWN ON THE FRONT STEERING WHEEL AND NOT THE REAR LANDING GEAR.

THERE IS ANOTHER POSSIBILITY FOR CASING THE FRONT END DAMAGE. WHICH IS THAT THE AIRCRAFT BOUNCED OFF THE REAR LANDING GEAR AND THEN HIT THE FRONT GEAR PRIOR TO THE REAR LANDING GEAR BEING FULLY ON THE RUNWAY.

DAMAGE TO THE AIRCRAFT FRONT GEAR AND ADJACENT FUSELAGE IS SUBSTANTIAL AND SHALL REQUIRE A COMPLETE TEAR DOWN OF THE FRONT GEAR TO DETERMINE THE FULL EXTENT.

## NTSB investigation

None matched to this report by aircraft and date. Search the NTSB's own records: https://data.ntsb.gov/carol-main-public/basic-search

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.