# NTSB WPR09LA480: Cessna R172K, N1055V, Page, AZ, July 1, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 1, 2009, 09:30 local (16:30 UTC) - Place: Page, AZ - Coordinates: 36.926109, -111.448333 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.9261&lon=-111.4483&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report June 28, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 75132 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09LA480 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75132/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75132 - Page: https://openairdocs.org/ntsb/WPR09LA480 ## Probable cause The pilot's improper landing flare and inadequate recovery from a bounced landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna R172K, 2 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072431), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna R172K, 19 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072431), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna R172K, 3 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072431), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Cessna R172K, 7 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072431), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The pilot reported that during a landing, the airplane touched down hard and bounced about 10 feet into the air. During the second bounce, the airplane flew in a nose-high pitch attitude until the airspeed bled off, then the airplane touched down hard a third time. The pilot taxied to the ramp and requested that a local mechanic inspect the airplane for obvious evidence of external damage. The mechanic accomplished an external inspection without looking inside the airplane or removing the engine's cowling and reported no obvious external damage. The pilot continued her cross-country flight and, a few days later, concluded the flight and returned the airplane to the fixed base operator. Several days after that, it was determined that the firewall had been substantially damaged, consistent with a hard landing accident. ## Factual narrative HISTORY OF FLIGHT On July 1, 2009, about 0930 mountain standard time, a Cessna R172K, N1055V, made a hard bounced landing at the Page Municipal Airport, Page, Arizona. The airplane was substantially damaged. Neither the private pilot nor the two passengers were injured. Visual meteorological conditions prevailed, and a visual flight rules flight plan had been filed for the personal flight. The airplane was operated by Spitfire Aviation, Santa Barbara, California. The flight was performed under the provisions of 14 Code of Federal Regulations Part 91, and it originated from Kingman, Arizona, about 0700. The pilot reported to the National Transportation Safety Board investigator that Spitfire Aviation's management had authorized her to rent N1055V for the several day duration round-robin cross-country flight. The pilot had previously rented airplanes from this flight school, where she had taken lessons from its owner and learned to fly. In the pilot's completed Safety Board "Aircraft Accident Report," form 6120.1, the pilot reported that she had departed from Santa Barbara on June 30, 2009, with two passengers. En route to Nevada, the pilot's first landing was at Kingman, where she completely refueled the airplane. The following morning, July 1, the pilot continued the flight and flew to Page, where she made a hard landing. Regarding the landing, the pilot stated that no crosswind existed during the traffic pattern approach and touchdown. The airplane touched down on its main landing gear and then bounced 10 feet into the air. The pilot further reported that during the second bounce, she recalled that the airplane was in a nose high attitude before it bounced the third (final) time. The last impact on the runway was the hardest, and the pilot stated that she was shaken up by the experience. Following the hard landing event, the pilot communicated with a certified flight instructor (CFI) employed by Spitfire Aviation, the flight school from whom she had rented the airplane. The pilot requested guidance from the CFI regarding possible reasons for her hard landing and follow-up action regarding the airplane. The CFI provided the pilot with the requested information and guidance. The pilot requested that a local airplane mechanic look at the airplane before she departed Page to continue her cross-country flight. The Safety Board investigator interviewed the airplane mechanic. The mechanic reported that he performed a brief visual "walk-around" inspection of the airplane. His work was performed for the pilot on a gratuitous basis. The mechanic stated that he did not remove the engine cowling, and no work order was opened. The mechanic reported he informed the pilot that he did not observe any obvious external structural damage. However, he did notice that oil had been leaking from the engine compartment, and the airplane's belly was dirty. On July 4, the pilot concluded the flight upon returning the airplane to Spitfire Aviation's Santa Barbara fixedbase operation. Wreckage Information The aforementioned CFI reported to the Safety Board investigator that on July 13, he went to Spitfire's maintenance hangar where N1055V was located. The airplane's engine cowling had been removed. The airplane's firewall was found bent so badly that it had twisted some of the airplane's instrument housings. According to the Spitfire mechanic who performed the initial structural examination for damage, major wrinkles in a "V" shape were noted on both the left and right side of the cockpit floor near the center pedestal, and sheet metal on the floor was deformed. The left and right side of the lower firewall was bent. The mechanic reported to the Safety Board investigator that the damage "was consistent with a hard landing event." The Safety Board investigator's subsequent review of Spitfire's records showed that replacement parts were ordered. The airplane had undergone a major structural repair that included repair of the firewall. ADDITIONAL INFORMATION Airplane Operation and Repair After the accident pilot returned the airplane to Spitfire Aviation on July 4, the operator placed the substantially damaged airplane back on its rental flight line. The airplane was subsequently rented. The Safety Board investigator interviewed the aforementioned CFI. The CFI stated that on July 11 he had detected binding of the airplane's elevator control system but elected to fly the airplane with a student/passenger. After completing the flight, the CFI alerted management of his observations, and the airplane was removed from service to undergo maintenance. Spitfire's "Daily Schedule" and rental records indicated that N1055V was listed as being continuously in maintenance from at least July 13, 2009, through September 7, 2009. There were no reports of other accidents or incidents involving N1055V between July 4 and July 13 when N1055V entered maintenance. Contrary to a written insurance loss statement signed by the pilot on August 17, which asserted that the bounced landing event had occurred upon landing in Santa Barbara on August 12, the pilot informed the Safety Board investigator that she had not flown N1055V since returning the airplane to Santa Barbara on July 4. The pilot verbally acknowledged to the Safety Board investigator that the hard landing had, in fact, occurred in Page on July 1, and that the FBO's owner had required her to report that the accident had occurred on a subsequent date. (See the Safety Board's docket for additional information regarding the pilot's first reported date for the landing mishap, airplane rental records, mechanic's statements and ordered parts.) Accident Notification and Documentation The National Transportation Safety Board did not receive notification of the accident pursuant to 49 CFR Part 830 from either personnel at Spitfire Aviation who observed the airplane's damaged condition, or from the accident pilot who had been informed of its damage. On October 20, 2009, Federal AviationAdministration (FAA) personnel received initial information from a former Spitfire Aviation employee that disclosed an accident had occurred that had not been reported. FAA personnel communicated relevant information about the suspected event to the Safety Board investigator. Spitfire Aviation's owner and its chief airplane mechanic refused to disclose to the Safety Board investigator information about the mishap. They refused access to airplane operation and maintenance records. As a result and after repeated requests for records, on January 22, 2010, the Safety Board issued Spitfire Aviation's owner a subpoena duces tecum. ## Aircraft - Registration: [N1055V](https://openairdocs.org/aircraft/N1055V), registered now, S/N R1722095, built 1976 (OpenAirDocs) - Reported make and model: CESSNA R172K - Registry model: [Cessna R172K](https://openairdocs.org/model/cessna-r172k) (registry code 2072431) (OpenAirDocs) - Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: R1722095 - Airframe hours: 7464 - Engines: Continental IO-360-K 195 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Spitfire Aviation, Inc. - Registered owner: Warner Aero Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 13, 2009, 57 hours before - Departed: IGM, Kingman, AZ - Destination: PGA, Page, AZ - Flight plan: VFR - Airport: PGA, Page Municipal, runway 15, 5,950 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 33; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review July 26, 2008; seat: left; flight hours: 194 total, 21 in this make and model, 36 as pilot in command, 22 in the last 90 days, 12 in the last 30 days, 5 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 37 °F - Altimeter: 29.98 inHg - Observed at: PGA ## 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 20090701054129A](https://openairdocs.org/incident/20090701054129A), Jul 1, 2009: Cessna R172K, Page, AZ, Substantial damage. There are conflicting reports on the actual date of the hard landing. There is a date of July 1, 2009 where the pilot reported to the aircraft rental location… ## Docket (17 files) The files NTSB released with the investigation on May 11, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75132. 10.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, and Attached GPS Data (item 1, .PDF, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337768&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20and%20Attached%20GPS%20Data-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, Spitfire Aviation (item 2, .PDF, 606 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337769&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20Spitfire%20Aviation-Redacted.PDF - Meteorological Information (item 3, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337770&FileExtension=.PDF&FileName=Meteorological%20Information-Master.PDF - FAA E-mail, Aircraft Documents (item 4, .PDF, 351 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337771&FileExtension=.PDF&FileName=FAA%20E-mail,%20Aircraft%20Documents-Redacted.PDF - FAA E-mail, Documents Received from D. Brisco (item 5, .PDF, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40365435&FileExtension=.PDF&FileName=FAA%20E-mail,%20Documents%20Received%20from%20D.%20Brisco-Redacted.PDF - Spitfire Operation, Personnel, & Aircraft (item 6, .PDF, 88 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337773&FileExtension=.PDF&FileName=Spitfire%20Operation,%20Personnel,%20%26%20Aircraft-Redacted.PDF - Spitfire's Daily Schedule (item 7, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337774&FileExtension=.PDF&FileName=Spitfire%27s%20Daily%20Schedule-Master.PDF - Aircraft Damage Claim (item 8, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337775&FileExtension=.PDF&FileName=Aircraft%20Damage%20Claim-Redacted.PDF - Aircraft Dispatch Records and Accounts (item 9, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337776&FileExtension=.PDF&FileName=Aircraft%20Dispatch%20Records%20and%20Accounts-Redacted.PDF - Aircraft Rental Records (item 10, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337779&FileExtension=.PDF&FileName=Aircraft%20Rental%20Records%20-Redacted.PDF - Fuel and Tie Down Receipts, Page, AZ (item 11, .PDF, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337778&FileExtension=.PDF&FileName=Fuel%20and%20Tie%20Down%20Receipts,%20Page,%20AZ-Redacted.PDF - Attorney E-mail & NTSB Subpoena (item 12, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40365438&FileExtension=.PDF&FileName=Attorney%20E-mail%20%26%20NTSB%20Subpoena-Redacted.PDF - Statement from Bill Peterson (item 13, .PDF, 14 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40339833&FileExtension=.PDF&FileName=Statement%20from%20Bill%20Peterson-Redacted.PDF - Record of Conversation - Mr. Brisco (item 14, .PDF, 88 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337781&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Mr.%20Brisco-Redacted.PDF - Record of Conversation - Mr. Martin (item 15, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337782&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Mr.%20Martin-Master.PDF - Record of Conversation - Ms. Rodriquez (item 16, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40337783&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Ms.%20Rodriquez-Master.PDF - Record of Conversation (Name Withheld) (item 17, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40365436&FileExtension=.PDF&FileName=Record%20of%20Conversation%20(Name%20Withheld)-Redacted.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.