# NTSB LAX04CA215: Piper PA-28R-200, N169JP, Galt, CA, April 25, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 25, 2004, 14:00 local (21:00 UTC) - Place: Galt, CA - Coordinates: 38.304721, -121.429443 - Nearby events: https://openairdocs.org/map.md?lat=38.3047&lon=-121.4294&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 29, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 59263 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX04CA215 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59263/pdf - Page: https://openairdocs.org/ntsb/LAX04CA215 ## Probable cause the pilot under instruction's failure to maintain an adequate airspeed on final and misjudged flare, which resulted in stall/mush and hard landing. The certified flight instructor's inadequate supervision and failure to initiate timely remedial action were also causal. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - airspeed - inadequate, dual student (cause) - supervision - inadequate, pilot in command(cfi) (cause) - remedial action - not performed, pilot in command(cfi) (cause) - flare - misjudged, dual student (cause) - stall/mush - encountered, dual student ## Analysis The pilot under instruction was slow on short final, flared, stalled, and made a hard landing. The pilot under instruction and certified flight instructor had made several uneventful landings. Both pilots reported that on the accident landing approach the pilot under instruction maintained a slow airspeed and misjudged the landing flare, which resulted in a hard landing. Both pilots indicated that there were no mechanical malfunctions or failures with the airplane or engine prior to the hard landing. ## Factual narrative On April 25, 2004, about 1400 Pacific daylight time, a Piper PA-28R-200, N169JP, made a hard landing at Franklin Field Airport, Galt, California. Ahart Aviation Services was operating the rental airplane under the provisions of 14 CFR Part 91. The certified flight instructor (CFI) and the commercial pilot undergoing instruction (PUI) were not injured; the airplane sustained substantial damage. The cross-country instructional flight departed Livermore Municipal Airport, Livermore, California, about 1300. Visual meteorological conditions prevailed, and no flight plan had been filed. In a written report, the PUI stated that the purpose of the flight was to practice short-field takeoff and landings on runway 27 at the Franklin Field Airport. While on short final, the PUI noted that the airplane appeared to be slow, indicating an airspeed of about 80 mile per hour. As he flared, the airplane touched down hard on the main landing gear. He initiated a go-around and attempted to return to the Livermore. While en route, he cycled the landing gear and noted that it would not lock in the retracted position. The landing gear was able to lock in the down position and the airplane landed uneventfully. The PUI further stated that both he and the CFI were not aware that the airplane sustained structural damage to several wing ribs until maintenance personnel examined the airplane the following morning. In a written report, the CFI stated that after completing several landings uneventfully the PUI was attempting another practice landing. The PUI maintained a slow airspeed on short final, and the airplane landed hard, touching down on the left main landing gear first. The PUI immediately initiated a go-around. On upwind, both pilots noticed that the landing gear transition light stayed illuminated. The light remained illuminated after several attempts to recycle the landing gear. On two separate Pilot/Operator Aircraft Accident Reports (NTSB Form 6120.1/2), both pilots indicated that there were no mechanical malfunctions or failures with the airplane or engine prior to the hard landing. ## Aircraft - Registration: [N169JP](https://openairdocs.org/aircraft/N169JP), registered now, S/N 28R-7235262, built 1972 (OpenAirDocs) - Reported make and model: Piper PA-28R-200 - Registry model: [Piper PA-28R-200](https://openairdocs.org/model/piper-pa-28r-200) (registry code 7102811) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28R-7235262 - Engines: Lycoming IO-360-CIC reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Ahart Aviation Services - Registered owner: Northern California Aviation LLC - Airworthiness certificate: Standard, Normal - Departed: LVK, Livermore, CA - Destination: Q53, Galt, CA - Airport: Q53, Franklin Field Airport, runway 27 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 32; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; flight hours: 1,800 total, 35 in this make and model, 1,500 as pilot in command, 200 in the last 90 days, 70 in the last 30 days - Pilot; age 26; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; flight hours: 395 total, 32 in this make and model, 255 as pilot in command, 32 in the last 90 days, 19 in the last 30 days ## Weather - Conditions: Visual (VMC), Day ## 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 20040425009769A](https://openairdocs.org/incident/20040425009769A), Apr 25, 2004: Piper PA28R200, Franklin, CA, Substantial damage. (-23) Pilot was practicing short field landings at the Franklin airport in preparation for a flight check. During the approach, the airspeed was slow which in… 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.