NTSB CAROL · Event
Event LAX98LA243
Aircraft involved
Probable cause & findings
A partial loss of engine power due to a disconnected throttle linkage, which was the result of an inadequate maintenance installation/inspection.
Factual narrative
On July 24, 1998, at 1228 hours Pacific daylight time, a Beech 35, N2720V, impacted terrain about 1/2 mile from the French Valley Airport in Temecula, California. The aircraft was destroyed and the private pilot, the sole occupant, sustained minor injuries. The personal flight originated at the Pauma Valley, California, airport at 1200 and no flight plan was filed. Visual meteorological conditions prevailed. The pilot reported that he entered a left downwind for runway 18. He reported that he pulled the power back, but the manifold pressure gauge indicated 25 inches of manifold pressure. The pilot stated that as he lined up with the runway but his airspeed was too high, so he decided to do a go-around. About midway down the field at 50 to 75 feet agl, he applied full throttle and retracted the landing gear. He reported that the engine remained at idle speed, indicating 900 to 1000 rpm. The pilot stated that he knew he wouldn't be able to land on the runway, so he turned about 20 degrees to the right and headed for an area where the terrain sloped down. He lowered the landing gear and aligned the aircraft with a street, but realized there were power lines in his way. The aircraft impacted the terrain about 1/2 mile from the airport. The pilot did not report experiencing any mechanical problems with the aircraft prior to the accident sequence. The Safety Board conducted a teardown inspection of the engine on July 30, 1998. There was no external evidence of catastrophic engine failure. The crankshaft was rotated with thumb compression and accessory gear train and valve action continuity was verified in all cylinders. The engine cowling was opened and it was observed that the throttle linkage was disconnected, with only about two threads of the connecting bolt (connects to throttle control rod end bearing) extending out of the throttle extension sleeve. According to the Beechcraft Parts Catalog schematic for the throttle control and landing gear warning switch, the throttle cable end is threaded through the landing gear warning switch actuator into the throttle cable extension sleeve. The throttle cable extension sleeve is threaded into the throttle control rod end bearing. There is an inspection hole in the throttle cable end for the mechanic to verify the engagement depth of the throttle cable. A copy of the throttle control schematic is appended to this file. The aircraft had only flown approximately 1 hour since receiving an annual inspection on July 1, 1998. The Beechcraft Maintenance manual checklist for a 100-hour/annual inspection directs the mechanic to check all engine controls and associated equipment for condition, attachment, alignment, and rigging. A copy of the relevant portions of the Beechcraft Maintenance Manual is appended to this file. The pilot initiated a go-around at 50 to 75 feet agl due to excessive airspeed, and as he applied full throttle, the engine went to idle. He turned the aircraft toward a street and impacted the terrain about 1/2 mile from the airport. The Safety Board conducted a teardown inspection of the engine and discovered that the throttle linkage was disconnected. The bolt that connects the throttle cable to the throttle control rod end bearing was protruding out of the extension sleeve by only two threads. The aircraft had only flown approximately 1 hour since the annual inspection earlier in the month. The pilot did not report any mechanical problems with the aircraft prior to the accident sequence. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_LAX98LA243.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 (stall, engine failure, go-around, maintenance). 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 2022 · Journal article (JAAER)
SMS for Part 135 Commuter and On-Demand Operations - The Practitioner’s Perspective
On May 15th, 2017, N452DA, a Learjet 35A operated by Trans-Pacific Air Charter, LLC, departed from Philadelphia to Teterboro, New Jersey (TEB) on a positioning flight under 14 Code of Federal Regulati…
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
Editor's Note: Celebrating 35 Years of Scholarly Excellence
A letter from the editor, Dr. Dahai Liu, on the JAAER's 35th anniversary.
- NASA NTRS 2024 · Presentation
Part 135 and Business Operator Low Altitude Events: An Analysis of ASRS Reports
This presentation provides an aviation SME's human factors analysis of selected Low Altitude and Controlled Flight Towards Terrain (CFTT) events involving Part 135 and business jet operators as report…
- NASA NTRS 2022 · Conference Paper
The In-time Aviation Safety Management System Concept for Part 135 Operators
Transformations of the National Airspace System, such as envisioned with Advanced Air Mobility, will enable improvements for managing and assuring safety for Part 135 transportation of passengers and …
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA)
Analysis of Part 135 Aircraft Accidents to Facilitate Flight Data Monitoring
The scheduled and on-demand air services with Title 14 Code of Federal Regulations (CFR) Part 135 certificate are operating with relatively less stringent safety program criteria compared to Part 121 …
Browse the full corpus — academia portal ↗