# NTSB LAX97LA111: Piper PA-28-236, N4341M, Palo Alto, CA, February 24, 1997 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 24, 1997, 10:00 local (18:00 UTC) - Place: Palo Alto, CA - Coordinates: 37.450153, -122.099578 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.4502&lon=-122.0996&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 31, 1997 - Report: Approved by Office Director - NTSB case key (mKey): 29731 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX97LA111 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/29731/pdf - Page: https://openairdocs.org/ntsb/LAX97LA111 ## Probable cause the pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise and subsequent overload failure of the nose gear. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - flare - improper, pilot in command (cause) - recovery from bounced landing - improper, pilot in command (cause) - porpoise/pilot-induced oscillation - inadvertent, pilot in command - Nose gear collapsed, landing - landing gear,nose gear - overload ## Analysis An air traffic controller observed the aircraft bounce after touchdown, then porpoise three times down the runway with each bounce increasing in amplitude. After the third bounce, the nose gear collapsed, and the aircraft slid off the left side of the runway. The wind was from 010 degrees at 15 knots. Examination of the aircraft revealed no evidence of a brake failure or other malfunction. ## Factual narrative On February 24, 1997, at 1000 hours Pacific standard time, a Piper PA-28-236, N4341M, porpoised on landing and veered off runway 30 at the Palo Alto, California, airport. The aircraft sustained substantial damage, and the pilot, the sole occupant, was not injured. Visual meteorological conditions existed for the personal flight and no flight plan was filed. The flight originated from San Jose, California airport at 0940. The pilot reported that maintenance personnel had been asked to check the right brake because it was ". . .extremely soft. Maintenance reported that they had flown the aircraft several times and had no trouble with the brake." The pilot stated that on taxi he noticed that the right brake was still ". . .extremely soft but that it worked if pumped up." The pilot reported that the landing was normal, but during the landing rollout the aircraft drifted to the left. "I made the decision to go around and went full power with right rudder. The aircraft continued to drift left as I applied power and exited the runway. . .after landing I observed both wind socks straight out but at different angles with respect to the runway. I perceived the wind to be at 15+ KIAS with gusts at 20+ KIAS perpendicular to runway heading." The Federal Aviation Administration (FAA) controller on duty at the time reported the winds were from 010 degrees at 15 knots. The controller observed the aircraft bounce on touchdown, become airborne again, then porpoise down runway 30 three times with each bounce increasing in amplitude. On the third bounce, the nose gear collapsed and the aircraft slid off the left side of the runway. An FAA inspector from San Jose stated that she observed marks on the landing runway and the grassy area where the airplane came to rest. Flight control and engine continuity were established on scene with no evidence of a brake malfunction or other anomalies noted. ## Aircraft - Registration: [N4341M](https://openairdocs.org/deregistered/N4341M-2018-01-19), registration cancelled 2018-01-19, S/N 28-8411010, built 1984 (OpenAirDocs) - Reported make and model: Piper PA-28-236 - Registry model: [Piper PA-28-236](https://openairdocs.org/model/piper-pa-28-236) (registry code 7102815) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-8411010 - Airframe hours: 2987 - Engines: Lycoming O-540 235 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Roger C. Hayward - Registered owner: J. David Powell - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 14, 1997, 2 hours before - Departed: SJC, SAN JOSE, CA - Destination: PAO, CA - Airport: PAO, Palo Alto, runway 30, 2,500 × 65 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; airline transport, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; seat: left; flight hours: 1,667 total, 23 in this make and model, 1,538 as pilot in command, 4 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Visibility: 30 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 19 °F - Altimeter: 30.00 inHg - Observed at: PAO ## 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 19970224001859A](https://openairdocs.org/incident/19970224001859A), Feb 24, 1997: Piper PA28236, Palo Alto, CA, Substantial damage. Porpoised landing until nose gear folded. Slid off runway. Blamed brakes. No defects found. ## Other investigations on N4341M (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 ERA11CA452](https://openairdocs.org/ntsb/ERA11CA452), Aug 14, 2011: Piper PA-28-236 (N4341M), Front Royal, VA, substantial damage. Probable cause: The pilot’s failure to attain the proper touchdown point. 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.