LAX08CA165 · Cessna 172M
Cessna 172M · Accident: hard landing
From San Carlos Airport (SQL) to an unrecorded destination
Event
- NTSB case
- LAX08CA165
- 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
- Unknown
- 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 172M
- 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
- N73403
- Operator
- Alex Al-Abed
- Onboard fatalities
- Unknown
- Route
- From San Carlos Airport (SQL), San Carlos, 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
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The certificated flight instructor (CFI) and a student were practicing landings. They made two successful landings, and were on approach for a third. Around this time, the recorded winds were from 250 degrees at 7 knots gusting to 18. When the airplane was 50 feet above ground level (agl), and over the runway numbers, the student reduced power to idle per the CFI's instructions. At that moment, the airplane encountered a sudden wind shift or gust, which abruptly caused the airplane to pitch down and bank to the right. The CFI added full power, and applied back pressure on the yoke, but was unable to keep the airplane from descending rapidly. The nose gear and right main landing gear violently struck the runway. The nose gear broke off, and the airplane bounced. The CFI regained control, and landed the airplane on both main landing gear while keeping the nose gear off the ground as long as possible. The nose settled on the broken nose gear strut, and the airplane stopped on the runway.
Probable cause
The flight instructor's inadequate compensation for the wind conditions, and his inadequate supervision of the student pilot. Factors contributing to the accident were a sudden wind shift and wind gusts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA165
- Event ID
- 20080701X00958
- Case number
- LAX08CA165
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 951fd5da827120ceee27ea9f93b2e64e936f822561f9dc2ef34c94b6a3681c6c; retrieved 2026-09-15T09:50:39.032Z.