NTSB CAROL · Event
Event LAX99LA279
Registry · N88408
FAA Aircraft Registry record.
Make / Model
BELLANCA 7ECA
Year of manufacture
1974 · 25 years old at event
Engine
LYCOMING 0-235 SERIES (115 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19741015
ADS-B equipped
Yes — Mode-S AC2F2A
Registrant of record
STEEL MIMI
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The failure of the no. 3 cylinder exhaust valve due to the operator's failure to adhere to recommended overhaul periods set by the engine manufacturer. A factor in the accident was the operator's failure to comply with the manufacturer's mandatory service bulletin.
Factual narrative
On August 21, 1999, at 1630 hours Pacific daylight time, a Bellanca 7ECA, N88408, experienced a loss of engine power in the takeoff initial climb at the Livermore, California, airport. During the attempted return to runway maneuver, the aircraft landed hard on a taxiway, ran off the pavement, and into a ditch. The aircraft, operated by Attitude Aviation under the provisions of 14 CFR Part 91 as an instructional flight, sustained substantial damage. The certified flight instructor (CFI) and a private pilot were not injured. Visual meteorological conditions existed for the recurrent training flight and no flight plan was filed. The CFI stated that the engine start and run-up were normal. At 500 feet above ground level (agl) in the initial climb, a partial loss of power was experienced. The CFI stated that the engine rpm's dropped suddenly from 2,600 to 1,500 "with roughness." He said that he took the controls from the student and found that an emergency landing could not be conducted straight ahead due to obstacles. He elected to perform a 180-degree turn back to the runway. As the turn was completed, a complete lost of engine power was experienced. Due to an airplane already on the runway, he aimed for the taxiway, and landed hard on the pavement. In the private pilot's written statement to the Safety Board, he said that the preflight, engine start, and taxi were normal. During the run-up, at 1700 rpm, a magneto check was conducted per the checklist procedures. He noted that the drop was approximately 100 rpm on each magneto, and the oil pressure and engine temperature were normal. They were cleared for takeoff and right closed traffic. When power was added it seemed normal and no discrepancies were noted with the acceleration to rotation speed. As they were climbing through 400 feet agl the engine began to run rough and subsequently a partial loss of power was experienced. The CFI immediately took the controls and declared an emergency. The pilot stated that the CFI entered a descending steep left turn to make it to runway 7R. He indicated that there "appeared to be no power from the engine," and the rate of descent was "too great." The CFI then contacted the tower to inform them that he was going to land on the adjacent taxiway for 7R. The pilot stated that there was insufficient altitude, the rate of descent was too fast, and the airplane struck the runway in a nose down left bank attitude. After the airplane departed the taxiway it came to rest in a drainage ditch parallel to the runway. The airplane was inspected by a Federal Aviation Administration (FAA) inspector on August 25, 1999, at Attitude Aviation. The investigation revealed that the number 3 exhaust valve of the Lycoming O-235-C1 engine had failed. The stem was found broken at the lower portion of the head. The FAA inspector reviewed the engine logbook and found that the engine had accumulated 3,711.0 hours since the last major overhaul, which was accomplished on November 30, 1993. In the CFI's written report to the Safety Board, he had requested on several separate occasions that the engine should be overhauled. He stated that the owner of the flight school stated that they would keep an eye on it. According to Textron-Lycoming Service Instruction number 1009AN dated November 5, 1999, the recommended time between overhaul periods for the O-235 model's (except F, G and J) is 2,400 hours. The Service Instruction letter indicates that all engines that do not accumulate the hourly period of time between overhauls specified in the letter are recommended to be overhauled in the twelfth year. A Textron Lycoming Mandatory Service Bulletin (SB) number 388B, issued on May 13, 1992, addresses the procedure to determine exhaust valve and guide condition. Compliance time for the engine inspections was specified to be at 400-hour intervals, or earlier, if valve sticking is suspected. The SB indicated that the failure to comply with the provisions in the publication could result in engine failure due to excessive carbon build-up between the valve guide and valve stem resulting in sticking exhaust valves or; broken exhaust valves which result from the excessive wear of the exhaust valve guide. No record of compliance with MSB 388B was noted during the logbook review. During the takeoff initial climb a partial loss of power was experienced, with the rpm's decreasing to 1,500 accompanied by roughness. The CFI took the controls from the student, made a 180-degree turn back to the runway, and landed hard on a taxiway. Both pilots indicated that there were no discrepancies noted with the preflight, engine start, taxi, or run-up. During the engine examination the number 3 exhaust valve was found broken, and the head found embedded in the piston. A review of the engine logbook revealed that the engine had accumulated 3,711.0 hours since the last major overhaul, which took place on November 30, 1993. According to the engine manufacturer, 2,400 hours or 12 calendar years is the maximum recommended time between overhaul. A Lycoming Mandatory Service Bulletin addresses the need to inspect exhaust valves and valve guides to prevent sticking and possible failure due to excessive guide wear. The bulletin recommends an inspection at 400-hour intervals. No record was found in the logbooks of compliance with the bulletin. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_LAX99LA279.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 (engine failure). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2022 · arXiv preprint
Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NASA NTRS 2019 · Conference Paper
Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Technical Memorandum (TM)
A simulator investigation of engine failure compensation for powered-lift STOL aircraft
A piloted simulator investigation of various engine failure compensation concepts for powered-lift STOL aircraft was carried out at the Ames Research Center.
- Semantic Scholar 2019 · Article (AIAA Scitech 2019 Forum)
Impact of Engine Failure Constraints on the Initial Sizing of Hybrid-Electric GA Aircraft
Potential advantages of hybrid-electric aircraft are fuel savings, lower emissions, and reduced noise. Since these aircraft generally apply multiple power sources, they can also be designed to sustain…
Browse the full corpus — academia portal ↗