# NTSB SEA02LA186: Piper PA-28-161, N132ND, Spokane, WA, September 28, 2002 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: September 28, 2002, 15:25 local (22:25 UTC) - Place: Spokane, WA - Coordinates: 47.61861, -117.54 - Nearby events: https://openairdocs.org/map.md?lat=47.6186&lon=-117.5400&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 8, 2003 - Report: Approved by Office Director - Parties: Spokane FAA FSDO - NTSB case key (mKey): 55813 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA02LA186 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55813/pdf - Page: https://openairdocs.org/ntsb/SEA02LA186 ## Probable cause The flight instructor's delay of the remedial action necessary to correct for the student pilot's error during the landing flare. Factors include the student pilot's misjudgment of the aircraft's height above the runway when he initiated the flare. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - remedial action - delayed, pilot in command(cfi) (cause) - flare - misjudged, dual student (contributing factor) ## Analysis The flight instructor told his student to make his landing on the second centerline stripe of the runway. After turning final, the student established a stabilized approach at the correct airspeed, but with a glideslope that would take him past the desired second stripe touchdown point. Because runway length was not a critical factor, the instructor decided to let the student continue on the higher than desired glideslope so that he would learn that it would take him past the desired point of touchdown. Reportedly, when the aircraft was still about 20 feet above the runway surface, the student reduced the power to idle and started to flare prematurely, and the aircraft ultimately leveled off about 10 feet above the runway. The instructor then advised the student that they were too high, and that if they landed from that height "...it would be rough." The student therefore added power (about one-quarter throttle) and lowered the nose in order to descend to a point closer to the runway. Soon after starting to make this adjustment, the student flared a second time, and the aircraft fell to the runway surface from an altitude that was still too high. As the aircraft began to fall toward the runway, the instructor reached for the throttle in order to initiate a go-around, but just as he made contact with it, the aircraft impacted the runway with sufficient force to result in substantial damage. At that point, the instructor took control of the aircraft, completed the landing sequence, and then taxied to an area where the aircraft could be checked for damage. According to the instructor, there was no indication of any problem with the engine or flight control system that would have contributed to the accident, and the FAA Inspector who looked at the aircraft did not find evidence of any such anomaly. ## Factual narrative On September 28, 2002, approximately 1525 Pacific daylight time, a Piper PA-28-161, N132ND, experienced a hard landing at Spokane International Airport, Spokane, Washington. The flight instructor and his student were not injured, but the aircraft, which is owned and operated by the University of North Dakota, sustained substantial damage. The 14 CFR Part 91 instructional flight, which departed the same location about 25 minutes earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation. According to the flight instructor, he told his student to make his landing on the second centerline stripe of the runway. After turning final, the student established a stabilized approach at the correct airspeed, but with a glideslope that would take him passed the desired second stripe touchdown point. Because runway length was not a critical factor, the instructor decided to let the student continue on the higher than desired glideslope so that he would learn that it would take him past the desired point of touchdown. Reportedly, when the aircraft was still about 20 feet above the runway surface, the student reduced the power to idle and started to flare prematurely, and the aircraft ultimately leveled off about 10 feet above the runway. The instructor then advised the student that they were too high, and that if they landed from that height "...it would be rough." The student therefore added power (about one-quarter throttle) and lowered the nose in order to descend to a point closer to the runway. Soon after starting to make this adjustment, the student flared a second time, and the aircraft fell to the runway surface from an altitude that was still too high. As the aircraft began to fall toward the runway, the instructor reached for the throttle in order to initiate a go-around, but just as he made contact with it, the aircraft impacted the runway with sufficient force to result in substantial damage. At that point, the instructor took control of the aircraft, completed the landing sequence, and then taxied to an area where the aircraft could be checked for damage. According to the instructor, there was no indication of any problem with the engine or flight control system that would have contributed to the accident, and the FAA Inspector who looked at the aircraft did not find evidence of any such anomaly. ## Aircraft - Registration: [N132ND](https://openairdocs.org/deregistered/N132ND-2018-01-10), registration cancelled 2018-01-10, S/N 2841222, built 1989 (OpenAirDocs) - Reported make and model: Piper PA-28-161 - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2841222 - Airframe hours: 10510 - Engines: Lycoming O-320-D3G 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: University Of North Dakota - Airworthiness certificate: Standard, Normal - Last inspection: AAIP, September 26, 2002, 9 hours before - Departed: GEG, Spokane, WA - Destination: GEG - Airport: KGEG, Spokane International, runway 25, 8,199 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 24; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; last flight review July 9, 2002; seat: right; flight hours: 1,021 total, 634 in this make and model, 946 as pilot in command, 106 in the last 90 days, 47 in the last 30 days, 4 in the last 24 hours - Student pilot; injuries: none ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 63 °F - Altimeter: 29.84 inHg ## 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 20020928026739A](https://openairdocs.org/incident/20020928026739A), Sep 28, 2002: Piper PA28161, Spokane, WA, Substantial damage. (-23) During flight training, aircraft made hard landing when student allowed airspeed to decay while about 10 feet in air. A/c landed left main landing gear… 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.