NTSB CAROL · Event
Event LAX95LA266
Registry · N7141J
FAA Aircraft Registry record.
Make / Model
CESSNA 172N
Seats / Engines
4 seats · 1 engine
ADS-B equipped
Yes — Mode-S A98D6D
Registrant of record
HUTT AVIATION INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's poorly planned approach, misjudged distance/altitude, and failure to make a go-around. The pilot inadvertently becoming lost and disoriented was a factor in this accident.
Factual narrative
On July 23, 1995, at 1423 hours Pacific daylight time, a Cessna 172N, N7141J, exited the departure end of runway 24 and nosed over at McClennan-Palomar Airport, Carlsbad, California. The pilot was completing a visual flight rules personal flight. The airplane, registered to and operated by the pilot, sustained substantial damage. The certificated private pilot, the sole occupant, received minor injuries. Visual meteorological conditions prevailed. The flight originated at El Monte Airport, El Monte, California, about 1310 hours. The pilot said in the aircraft accident report form that he initially called the tower when he was over the powerplant, about 4 miles west-southwest of the airport. The controller gave the pilot some instructions, however, he did not hear them clearly and continued to the downwind leg and reported his position. He did not hear any reply. The pilot then executed a 360-degree turn and again contacted the tower; the local controller told him that he did not have the airplane in sight. The pilot made another 360-degree turn. During the turn, the controller instructed the pilot to remain at 1,500 feet (mean sea level) and asked if he had the runway in sight. The pilot said he did, and at this time the airplane was about 1,000 feet from the threshold. The controller cleared the pilot to land. The pilot reduced the power and began the landing approach. He said that the airplane was past midfield when it touched down. He said that he was unable to stop the airplane and knew that he could not go-around. The airplane exited the departure end of the runway. When the airplane entered the rough/uneven dirt, the nose gear collapsed and the airplane nosed over onto its back. National Transportation Safety Board investigators reviewed the Palomar Airport recorded communications media between the pilot and the local controller. The communications media revealed that the local controller was handling many airplanes and that the pilot reported over the powerplant. After giving another airplane instructions, the local controller provided landing instructions to the pilot. The controller then instructed the pilot to press the identification mode of the transponder. The pilot said that the mode was inoperative. The local controller did not have radar or visual contact with N7141J and instructed the pilot to report on the downwind leg. Later the pilot became disoriented and could not find the airport. Another airplane spotted the accident airplane east of the airport and informed the local controller. The local controller observed the airplane and made positive visual identification with it. The local controller helped the pilot with verbal instructions to the airport. The pilot said that he had the airport in sight and the local controller cleared the pilot to land. The pilot made a left turn toward the runway, but again became disoriented. The local controller gave the pilot verbal instructions and guided him through a missed approach procedure and reentry into the traffic pattern. The pilot followed the instructions. While on the downwind leg, the local controller asked the pilot if he had the runway in sight, and if so, was he able to land. The pilot said he had the runway in sight and that he could land. The local controller cleared the pilot to land. There were no further communications between the pilot and the local controller. One ground witness said that he heard and recorded the communications between the pilot and the local controller. He said that the pilot sounded confused during his communications with the local controller. He said that the airplane was high on final approach and then made an "S" turn. He said that the airplane entered "ground effect" when it was abeam the tower. The flaps were retracted and the airplane was flying between 70 and 80 knots. The airplane landed between 400 and 500 feet from the end of the runway. The airplane made a left turn and then ran off the end of the runway. The three controllers in the tower said that the airplane touched down west of the second taxiway intersection of the runway at a high speed. Two of the controllers said the flaps were retracted; the other controller said that the pilot lowered about 10 degrees of flaps before touching down. During the landing roll, the airplane exited the right side of the departure end of the runway and went down the embankment. WHEN THE PILOT APPROACHED THE DESTINATION AIRPORT HE REPORTED HIS POSITION TO THE LOCAL CONTROLLER. THE LOCAL CONTROLLER INSTRUCTED THE PILOT TO ENTER THE DOWNWIND LEG AND TO SQUAWK IDENT. THE PILOT SAID THAT THE TRANSPONDER IDENT MODE WAS INOPERATIVE AND THE CONTROLLER TOLD HIM THAT HE WAS NOT IN SIGHT AND INSTRUCTED HIM TO REPORT ON THE DOWNWIND LEG. THE PILOT BECAME DISORIENTED AND CONFUSED. WITH THE ASSISTANCE OF ANOTHER AIRPLANE, THE CONTROLLER WAS ABLE TO VISUALLY IDENTIFY THE ACCIDENT AIRPLANE AND PROVIDE THE PILOT VERBAL GUIDANCE TO THE AIRPORT. AFTER MAKING ONE MISSED APPROACH, THE PILOT TOLD THE CONTROLLER HE HAD THE RUNWAY IN SIGHT. THE CONTROLLER CLEARED THE PILOT TO LAND. THE CONTROLLERS IN THE TOWER CAB AND ONE GROUND WITNESS SAID THE AIRPLANE'S FINAL APPROACH SPEED WAS FAST AND ITS FLAPS WERE RETRACTED. THE AIRPLANE TOUCHED DOWN ABOUT 500 FEET FROM THE END OF THE RUNWAY. THE AIRPLANE EXITED THE END OF THE RUNWAY, WENT DOWN THE EMBANKMENT, AND NOSED OVER. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_LAX95LA266.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 (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗