FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX92LA238 · Cessna 177A

7 Jun 1992 · Mariposa, CA, United States

Cessna 177A · Accident: hard landing

From Fresno Chandler Executive Airport (FCH) to an unrecorded destination

Report a problem

Event

NTSB case
LAX92LA238
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 177A

Aircraft type
Cessna 177
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3144T
Operator
Robert G. Fairbourn · private individual
Onboard fatalities
Unknown
Route
From Fresno Chandler Executive Airport (FCH), Fresno, CATo not recorded
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Hard landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Flare, misjudged
  • Pilot in command › Go-around, not selected
  • Pilot in command › Planned approach, poor
  • Pilot in command › Proper touchdown point, not obtained
  • Pilot in command › Recovery from bounced landing, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

IN AN INTERVIEW, THE PILOT SAID THAT WHILE HE WAS IN THE TRAFFIC PATTERN TO LAND, HE TURNED BASE TOO SOON. HE SAID THE AIRPLANE'S AIRSPEED WAS A LITTLE FAST AND HE WAS A LITTLE HIGH. HE SAID HE PLACED THE AIRPLANE IN A SLIP. HE SAID HE LEVELED THE AIRPLANE OVER THE RUNWAY NUMBERS, BUT THE AIRSPEED WAS ABOUT 20 MILES PER HOUR TOO FAST. HE SAID HE LANDED THE AIRPLANE HARD ON ALL THREE LANDING GEAR AND THE AIRPLANE BEGAN TO PORPOISE. HE SAID THE AIRPLANE 'BOUNCED ABOUT 4 TO 5 TIMES.' HE ALSO SAID HIS LACK OF TOTAL EXPERIENCE DID NOT HELP AND THAT HE PROBABLY SHOULD HAVE EXECUTED A GO-AROUND.

Probable cause

THE PILOT'S POORLY PLANNED APPROACH FOR LANDING, HIS FAILURE TO INITIATE A GO-AROUND, HIS FAILURE TO OBTAIN THE PROPER TOUCHDOWN POINT, HIS MISJUDGMENT OF THE TOUCHDOWN FLARE, AND HIS IMPROPER RECOVERY FROM A BOUNCED LANDING. A FACTOR IN THIS ACCIDENT WAS THE PILOT'S LACK OF TOTAL AERONAUTICAL EXPEREINCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX92LA238
Event ID
20001211X14900
Case number
LAX92LA238
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a8bb80423b2e34e009ebff994a6446577c10cfb911827a33ec39d7f895ca7874; retrieved 2026-09-23T03:05:08.538Z.