LAX03LA094 · Luscombe T-8F
Luscombe T-8F · Accident: loss of control on ground/water during landing
From Gillespie Field (SEE) to Gillespie Field (SEE)
Event
- NTSB case
- LAX03LA094
- 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
Luscombe T-8F
- Aircraft type
- Luscombe T-8
- 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
- N1822B
- Operator
- John A. Hammerstrand · private individual
- Onboard fatalities
- Unknown
- Route
- From Gillespie Field (SEE), El Cajon, CATo Gillespie Field (SEE), El Cajon, 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
- Landing · landing roll
- 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(cfi) › Compensation for wind conditions, inadequate
- Pilot in command(cfi) › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During landing rollout, the airline transport pilot encountered a left crosswind, lost directional control, collided with a sign, applied engine power thereby initiating a go-around and finally collided with terrain. Previously, the second pilot had performed three takeoffs and landings in the traffic pattern. The certificated airline transport pilot (ATP) performed the fourth landing on runway 27R. During rollout he pulled the control stick aft and left. The airplane veered left, directional control was lost, and the airplane collided with a taxiway sign. Thereafter, the ATP applied full engine power to go around. The airplane veered right, exited the right side of the runway, and became airborne. While in ground effect, the airplane's right wing tip impacted a nearby dirt embankment. The airplane came to rest in a grassy field on airport property. The ATP indicated that during the attempted landing the left crosswind increased in speed and a gust was encountered. He estimated that the wind was from 220 degrees at 10 knots, with an occasional gust to 14 knots.
Probable cause
The pilot's inadequate compensation for the crosswind conditions and loss of directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA094
- Event ID
- 20030303X00273
- Case number
- LAX03LA094
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-02-24.
- API snapshot SHA-256: 0631f1808f249666950908bf46c44d27db5d85ca4e4e3540e997dbd7327cc7d5; retrieved 2026-09-22T09:34:50.013Z.