NTSB CAROL · Event
Event LAX97LA252
Registry · N9099G
FAA Aircraft Registry record.
Make / Model
CESSNA 182N
Year of manufacture
1971 · 26 years old at event
Engine
CONT MOTOR O-470 SERIES (230 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19710512
ADS-B equipped
Yes — Mode-S AC9435
Registrant of record
REGISTRATION PENDING
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Failure of maintenance personnel to adequately repair the pitch trim system and ensure that it was properly rigged, and the pilot's failure to maintain pitch control due to the distraction at liftoff of the mistrim condition.
Factual narrative
On July 17, 1997, at 1810 hours Pacific daylight time, a Cessna 182N, N9099G, porpoised down runway 22L on takeoff from Sacramento Mather Airport, Sacramento, California, and collapsed the nose landing gear. The airplane sustained substantial damage, and the pilot/owner, the sole occupant, was not injured. Visual meteorological conditions existed for the personal flight to the Rio Vista, California, airport. No flight plan was filed. The pilot reported that new seat locks and an avionics system had been installed, and that some additional problems had arisen while the mechanics were working on the aircraft. When the mechanics had shown the seat locks to the pilot, he noted that they would not slide and would jam on the rail. The aircraft was moved back into the maintenance hangar to be repaired. During the repair, the pilot performed a preliminary walk around, and noted that the trim tab was in an elevated position. He also found that the he was unable to remove the dipstick. He informed maintenance personnel, who repositioned the dipstick tube. The pilot stated that after the work was completed, the aircraft was moved out of the hangar. He started the engine and remembered that the trim tab was in an up position. The pilot stated that he rolled the trim wheel down into the takeoff position, and attempted to make a radio transmission, but was unable to do so. He shut the aircraft down and found the mechanic who had worked on the aircraft. The mechanic discovered that one of the wire connections for the radio was in the wrong opening. The pilot reported that he started the aircraft and transmitted his intentions to taxi to runway 22L without further incident. The pilot said that once the aircraft reached 60-65 knots, he applied back pressure to the yoke to lift the nose off the ground and the yoke felt heavier than what he was used to. As the nose came off the ground he released some of the back pressure on the yoke to gain airspeed. Once the aircraft became airborne it bounced back onto the runway. The pilot reported that he ". . .pulled the yoke back and then it bounced higher and harder." He realized something was different than a previous experience and compensated by reducing the power after the second bounce. The aircraft came down nose wheel first, collapsed the nose wheel, and the propeller struck the runway. The pilot further reported that he is certain that the trim indicator did not provide a ". . .true reading of the trim position." A Federal Aviation Administration (FAA) inspector from the Sacramento Flight Standards District Office inspected the airplane. Flight control continuity could not be established due to cockpit floor area impact damage. The inspector noted that in the trim tab travel "up" direction the stop occurred at 25 degrees tab deflection. Cessna specification states that the "up" stop is at 25 degrees plus/minus 2. In the trim travel "down" direction, the stop was at 10 degrees, with the Cessna specification as 15 degrees plus/minus 1. The "down" limit was limited by "trim cable stop." The FAA Aircraft Type Certificate Data Sheet notes that the total stop-to-stop trim tab travel should be 43 degrees, including the plus/minus degrees. The inspector found that the total trim available in the aircraft was 35 degrees. The inspector reported that "while the total trim travel was favoring the trim tab travel up/nose down attitude, it was off-centered by only 5 degrees." The inspector did note that when the trim was set to the takeoff position inside the aircraft, the trim tab was measured at an approximate 30-degree tab up or nose down position. He further noted that the trim indicator pointer "slipped easily from one trim wheel groove into another while actuating the trim wheel was moved with normal force." The inspector reported that this would have allowed an erratic trim tab position indication. The inspector stated that there was also noticeable deformation to the trim wheel pointer assembly that was not postcrash related. The Safety Board conducted a review of the maintenance records. On June 27, 1997 an entry on a squawk sheet was made where the pitch trim wire had jumped its groove. The corrective action was to reposition the pitch trim indicator to center travel in the window. This repair was made by the same facility that had worked on the aircraft the day of the accident. While performing the walk around inspection the pilot noted the elevator trim tab was in an elevated position. After starting the engine the pilot repositioned the trim wheel inside the cockpit to the takeoff position. During takeoff rotation the pilot eased back on the yoke and reported that the aircraft felt heavier than usual. As the aircraft came off the ground, the pilot released some of the back pressure and the aircraft struck the runway. The pilot pulled the yoke back and the aircraft bounced higher and harder. After the second bounce the pilot reduced the power, the nose wheel struck the runway and collapsed the nose landing gear. Approximately 1 month before the accident a discrepancy was reported indicating that the pitch trim wire had jumped its groove. The same facility that had worked on the aircraft the day of the accident had repaired the pitch trim wire by repositioning the pitch trim indicator to center travel in the window. The aircraft's type certificate data sheet notes that the total trim tab travel should be 43 degrees including the plus/minus tolerances. An FAA inspector examined the aircraft and found that the total trim travel available was 35 degrees. The inspector reported that the total trim travel favored the nose down attitude, but it was off-centered by only 5 degrees. The cockpit indicator was found to move easily from grove to grove. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_LAX97LA252.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, 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 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗