FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX87LA008 · Cessna 172N

3 Oct 1986 · Hayward, CA, United States

Cessna 172N · Accident: loss of control in flight on approach

From San Carlos Airport (SQL) to Hayward Executive Airport (HWD)

Report a problem

Event

NTSB case
LAX87LA008
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 172N

Aircraft type
Cessna 172
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
N6366D
Operator
Unknown
Onboard fatalities
Unknown
Route
From San Carlos Airport (SQL), San Carlos, CATo Hayward Executive Airport (HWD), Hayward, CA
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
Approach · VFR pattern final
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 in flight
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 › Compensation for wind conditions, not performed
  • Pilot in command › Go-around, not selected
  • Pilot in command › Proper alignment, not maintained
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

A CESSNA 172N LANDED ADJACENT TO RWY 28L. ACCORDING TO THE FAA THE SOLO STUDENT PLT WAS UNABLE TO CORRECT FOR A STRONG WIND AND LANDED IN A GRASS AREA SOUTH OF THE RUNWAY. THE WINDS WERE REPORTED FROM 360 DEG AT 17 KTS AT THE TIME OF THE ACCIDENT. THE PILOT'S OPERATING HANDBOOK FOR THE CESSNA 172N STATES, 'THE MAXIMUM ALLOWABLE CROSSWIND VELOCITY IS DEPENDENT UPON PILOT CAPABILITY AS WELL AS AIRCRAFT LIMITATIONS. WITH THE AVERAGE PILOT TECHNIQUE, DIRECT CROSSWINDS OF 15 KNOTS CAN BE HANDLED WITH SAFETY. THE STUDENT PLT INDICATED ON HIS PILOT/OPERATOR ACCIDENT REPORT THAT HE HAD ACCUMULATED A TOTAL OF 15 HRS FLIGHT EXPERIENCE, 4.1 HRS OF WHICH AS PIC.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX87LA008
Event ID
20001213X34985
Case number
LAX87LA008
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: 87df640c0cbb60af58693cc8d2e09e71990e832a5e918a488fa34296a5711a47; retrieved 2026-09-23T13:55:35.114Z.