# NTSB LAX96LA235: Cessna 172N, N6261D, Avalon, CA, June 16, 1996 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 16, 1996, 15:02 local (22:02 UTC) - Place: Avalon, CA - Coordinates: 33.379611, -118.449493 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.3796&lon=-118.4495&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report August 25, 1997 - Report: Approved by Office Director - NTSB case key (mKey): 29474 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX96LA235 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/29474/pdf - Page: https://openairdocs.org/ntsb/LAX96LA235 ## Probable cause the pilot's failure to initiate a landing flare, which resulted in a bounced landing and porpoise, and his loss of directional control during an attempt to initiate a go-around with insufficient airspeed, which resulted in an inadvertent stall/mush and collision with parked aircraft. A visual illusion created by the runway gradient was a factor in this accident. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - flare - not performed, pilot in command (cause) - visual illusion, pilot in command (contributing factor) - Loss of control - on ground/water, landing - aborted - recovery from bounced landing - performed, pilot in command - airspeed(vr) - not attained, pilot in command (cause) - stall - encountered, pilot in command (cause) - directional control - not maintained, pilot in command (cause) - On ground/water collision with object, landing - aborted - object - aircraft parked/standing - ground loop/swerve - inadvertent, pilot in command (cause) ## Analysis Ground witnesses stated that the pilot did not flare and the aircraft touched down hard on the nose wheel and porpoised twice. On the second bounce the aircraft veered off the runway and toward a line of parked aircraft. The pilot attempted to recover by adding power; however, the aircraft stalled, impacted the ground, and collided with three parked aircraft. ## Factual narrative On June 16, 1996, at 1502 hours Pacific daylight time, a Cessna 172N, N6261D, collided with three parked aircraft after a hard landing at Catalina airport, Avalon, California. The aircraft sustained substantial damage; however, neither the private pilot nor his three passengers were injured. The aircraft was being operated as a personal flight by Pars Air when the accident occurred. The flight originated in Santa Ana, California, about 1430 on the day of the accident. Visual meteorological conditions prevailed at the time and no flight plan had been filed. The airport manager reported that he first observed the aircraft in the traffic pattern on approach to runway 22. During the landing sequence the aircraft failed to flare and touched down on the nose wheel. The aircraft porpoised twice and on the second bounce, the pilot attempted to recover. The aircraft veered off the runway and stalled about 25 to 30 feet in the air, hit the ground, and subsequently struck three other parked aircraft. The pilot reported that he was making a normal approach with 40 degrees of flaps. On touchdown he bounced once and then bounced a second time, when the aircraft struck a hole in the runway. The nosewheel began to shake severely and he applied back pressure on the control wheel but thought at this time he was nearing the end of the runway. He intentionally turned left to avoid running off what he thought was the departure end. A second witness, who was a coworker of the airport manager, reported that he heard the engine accelerate during the accident sequence. He also stated that, although there was some spalling of the runway surface, there were no holes in the runway at the time of the accident. According to the NOAA Airport/Facility Directory, pilots cannot see aircraft on opposite ends of the runway due to the runway gradient. The other aircraft involved were identified as: a Beech G18S, N9375Y; a Grumman AA-5, N5439L; and another Cessna 172N, N6441D. A postaccident inspection of the aircraft revealed that the flaps were still extended to 40 degrees and the aircraft was trimmed nose down. ## Aircraft - Registration: [N6261D](https://openairdocs.org/aircraft/N6261D), registered now, S/N 17272672 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17272672 - Airframe hours: 5465 - Engines: Lycoming O-320-H2AD 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Mamood Namdar - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 3, 1996, 9 hours before - Departed: SNA, SANTA ANA, CA - Destination: AVX - Airport: AVX, Catalina, runway 22, 3,240 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 43; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 111 total, 11 in this make and model, 36 as pilot in command, 19 in the last 90 days, 16 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Observed at: AVX ## 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 19960616014029A](https://openairdocs.org/incident/19960616014029A), Jun 16, 1996: Cessna 172N, Avalon, CA, Substantial damage. Lost control on hard landing. Bounced porpoised. Drifted into parked aircraft. Failed flare. Had hit nose first. 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.