# NTSB LAX05CA275: Cessna 172S, N106ED, Edwards AFB, CA, July 20, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 20, 2005, 06:50 local (13:50 UTC) - Place: Edwards AFB, CA - Coordinates: 34.905277, -117.883613 - Nearby events: https://openairdocs.org/map.md?lat=34.9053&lon=-117.8836&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2005 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 62314 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX05CA275 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62314/pdf - Page: https://openairdocs.org/ntsb/LAX05CA275 ## Probable cause the pilot's misjudged flare and inadequate recovery technique from the subsequent bounces. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - flare - misjudged, pilot in command (cause) - porpoise/pilot-induced oscillation - encountered, pilot in command (cause) - recovery from bounced landing - inadequate, pilot in command (cause) ## Analysis The airplane landed hard and porpoised, damaging the nose wheel and firewall. The pilot was making a repositioning flight from the south runway complex to the main base runway (approximately 1/4 mile distance). The pilot departed runway 24 and landed on runway 04. Upon touchdown, the airplane hit the runway hard and bounced back into the air. The pilot tried to recover, but on the second landing attempt, the airplane hit the runway even harder. The airplane bounced one or two more times before the pilot was able to complete the landing. After the pilot parked the airplane, he completed a post flight inspection, and found damage to the propeller and to the nose wheel. Further inspection revealed damage to the firewall. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. ## Factual narrative On July 20, 2005, about 0650 Pacific daylight time, a Cessna 172S, N106ED, made a hard landing at Edwards Air Force Base, Edwards, California. Edwards Aero Club was operating the airplane under the provisions of 14 CFR Part 91. The private pilot, the sole occupant, was not injured; the airplane sustained substantial damage. The local personal flight departed about 0649. Visual meteorological conditions prevailed, and no flight plan had been filed. The approximate global positioning system (GPS) coordinates of the accident were 34 degrees 54.33 minutes north latitude by 117 degrees 53.02 minutes west longitude. The operator contacted the Federal Aviation Administration, Flight Standards District Office (FSDO), Van Nuys, California, on July 20, 2005. The FSDO notified the National Transportation Safety Board of this accident on August 22, 2005. The pilot reported that while making a repositioning flight from the south runway complex to the main base runway (approximately 1/4 mile distance), the pilot departed runway 24 and landed on runway 04. Upon touchdown, the airplane hit the runway hard and bounced back into the air. The pilot tried to recover, but on the second landing attempt, the airplane hit the runway even harder. The airplane bounced one or two more times before the pilot was able to complete the landing. After the pilot parked the airplane, he completed a post flight inspection, and found damage to the propeller and to the nose wheel. Further inspection revealed damage to the firewall. On August 29, 2005, the operator submitted a Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2). The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. ## Aircraft - Registration: [N106ED](https://openairdocs.org/aircraft/N106ED), registered now, S/N 172S8486, built 2000 (OpenAirDocs) - Reported make and model: Cessna 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8486 - Airframe hours: 3233.2 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Edwards Aero Club - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: AAIP, July 1, 2005, 10.6 hours before - Departed: EDW, EDWARDS, CA - Destination: EDW, EDWARDS, CA - Airport: EDW, Edwards Afb, runway 04, 15,013 × 300 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 39; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review June 1, 2005; seat: left; flight hours: 109 total, 50 in this make and model, 65 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 6 knots - Visibility: 36 statute miles - Lowest ceiling: none ## 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 20050720019829A](https://openairdocs.org/incident/20050720019829A), Jul 20, 2005: Cessna 172S, Edwards, CA, Substantial damage. (-23) On 07/20/05 at 0745 PDT, [privacy data omitted] the pilot in command and sole occupant of N106ED, a Cessna 172, landing on Edwards Afb main base runway… ## Other investigations on N106ED (1) 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. - [NTSB GAA19CA282](https://openairdocs.org/ntsb/GAA19CA282), Apr 28, 2019: Cessna 172 (N106ED), Edwards Air Force Base, CA, substantial damage. Probable cause: An undetermined event, which resulted in substantial damage to the airplane for reasons that could not be determined based on the available evidence. 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.