NTSB CAROL · Event
Event LAX96LA301
Registry · N8124S
FAA Aircraft Registry record.
Make / Model
PIPER PA-28-236
Year of manufacture
1979 · 17 years old at event
Engine
LYCOMING 0-540 SERIES (250 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19791018
ADS-B equipped
Yes — Mode-S AB13BF
Registrant of record
BAUSO KENNETH
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's decision to turn off the runway while at an excessive speed that did not allow him to maintain directional control of the aircraft.
Factual narrative
On August 4, 1996, at 1616 hours Pacific daylight time, a Piper PA-28-236, N8124S, collided with an airport taxiway sign after exiting runway 19L on taxiway Juliet at John Wayne Airport, Santa Ana, California. The aircraft sustained substantial damage; however, neither of the two pilots onboard were injured. The aircraft was being operated as a public-use flight by the Civil Air Patrol (CAP) when the accident occurred. The flight originated in Big Bear, California, at 1600. Visual meteorological conditions prevailed for the personal flight and no flight plan was filed. According to the pilot, the aircraft was making a full-stop landing on runway 19L. The aircraft made the approach with full flaps and a final approach airspeed of 70 knots, touching down just past the numbers. As the aircraft slowed, the pilot planned to turn off on taxiway Juliet that is located at approximately the midfield point. When he started his turn off, he applied the brakes but obtained no braking action. Seeing several other aircraft in front of him, the pilot veered off the right side of the ramp. As he was attempting to maneuver around some obstructions, the aircraft's left wing struck a taxiway sign. After the collision, the aircraft returned to parallel taxiway Charlie and was cleared to east parking at Martin Aviation. The CAP reported that there was no record of a flight plan having been filed. A postaccident inspection revealed a 12-inch-wide gash on the underside of the left wing. The gash was located between the third and fourth ribs, and extended from the leading edge aft to the aileron. The main outboard spar assembly was torn and separated. The upper wing surface was wrinkled and bowed aft of the initial point of impact. A joggle bend was noted at the midpoint of the left aileron, and the inboard edge of the left flap had impinged on the fuselage. A representative of the aircraft manufacturer estimated that, under the conditions described by the pilot, the aircraft would have required approximately 900 feet from the touchdown point to make a full stop on the runway. FAA inspectors reported they found S-shaped skid marks on the runway/taxiway at Juliet on the east side of runway 19L. The ATCT ground controller did not report any potential conflicts between taxiing aircraft and the accident aircraft at the time of the accident. The CAP aircraft manager reported that the aircraft braking system was inspected after the accident and was found to function properly. The CAP California Wing safety officer also reported that the same pilot had been involved in a similar runway excursion incident with a Cessna 206 on April 23, 1996. During that incident, the pilot lost directional control of the aircraft while landing. He attributed the loss of control to an "uncommanded turn." The aircraft made an intended full flap, full stop approach, touching down just past the numbers. As the aircraft slowed, the pilot began a turn toward the taxiway at midfield. He applied the brakes, but said he obtained no braking action. Seeing several other aircraft in front of him, the pilot veered off the side of the taxiway. As he was attempting to maneuver around obstructions, the aircraft's wing struck a taxiway sign. FAA inspectors reported they found S-shaped skid marks on the runway/taxiway at Juliet on the east side of runway 19L. The ATCT ground controller did not report any conflicts with taxiing aircraft. The CAP aircraft manager reported that the aircraft braking system was inspected after the accident and was found to function properly. The pilot had been involved in a previous incident in which he experienced a loss of directional control while landing. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96LA301.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2017 · Conference paper
Energy Safety Management: Mitigating Loss of Control Inflight
Under the new Airman Certification Standards (ACS), the Federal Aviation Administration (FAA) has mandated for the first time that private and commercial pilot candidates demonstrate understanding of …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
Browse the full corpus — academia portal ↗