FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX90LA294 · Cessna 180H

21 Aug 1990 · San Carlos, CA, United States

Cessna 180H · Accident: loss of control on ground/water during landing

From Watsonville Municipal Airport (WVI) to San Carlos Airport (SQL)

Report a problem

Event

NTSB case
LAX90LA294
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 180H

Aircraft type
Cessna 180
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
N2790X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Watsonville Municipal Airport (WVI), Watsonville, CATo San Carlos Airport (SQL)
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
Loss of control on ground/water
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 › Directional control, not maintained
  • Pilot in command › Ground loop/swerve, inadvertent
  • Pilot in command › Rudder, improper use of

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

NTSB narrative

ACCORDING TO THE PILOT, THE AIRCRAFT WAS IN A THREE POINT LANDING FLARE ATTITUDE JUST ABOVE THE RUNWAY WHEN THE NOSE BEGAN TO YAW TO THE RIGHT. THE PILOT SAID THAT HE APPLIED A LEFT RUDDER INPUT TO CORRECT THE YAW; HOWEVER, THE AIRCRAFT TOUCHED DOWN PRIOR TO THE RUDDER INPUT CORRECTING THE YAW ANGLE. THE PILOT REPORTED THAT AFTER THE MAIN WHEELS TOUCHED THE RUNWAY HE LOST CONTROL OF THE AIRCRAFT AND IT GROUND LOOPED. EXAMINATION OF THE PILOT'S REPORTED FLIGHT TIME REVEALED THAT HE HAS LESS THAN 30 HOURS OF TIME IN THE CESSNA 180H AIRCRAFT, AND, LESS THAN 50 HOURS OF TOTAL TAIL WHEEL FLIGHT EXPERIENCE.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN DIRECTIONAL CONTROL OF THE AIRCRAFT DURING THE LANDING. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT'S LACK OF TOTAL EXPERIENCE IN TAILWHEEL AIRCRAFT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX90LA294
Event ID
20001212X24057
Case number
LAX90LA294
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: d679b709d0eeaf61c89454b81200db65181a7ebd80dfdcc81e0aa85ee0fb50ac; retrieved 2026-09-23T05:24:27.629Z.