LAX82DA300 · Taylorcraft DCO-65
Taylorcraft DCO-65 · Accident: loss of control on ground/water during landing
From Reid-Hillview Airport of Santa Clara County (RHV) to Los Banos, CA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination and aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX82DA300
- 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
Taylorcraft DCO-65 Possible conflict
- Aircraft type
- Taylorcraft DCO-65
- 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
- N47325
- Operator
- Mary Ann Buyuklian
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Reid-Hillview Airport of Santa Clara County (RHV), San Jose, CATo Los Banos, 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 › Directional control, not maintained
- Pilot in command › Ground loop/swerve, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING ARRIVAL, THE PILOT ENTERED TRAFFIC TO LAND ON RUNWAY 31 WITH A WIND FROM 130 DEG AT 5 KTS. THE FIRST APPROACH TO LAND WAS HIGH, SO A GO-AROUND WAS MADE. ON THE SECOND APPROACH, THE AIRCRAFT WAS LOW AND FAST. REPORTEDLY, THE AIRCRAFT BEGAN TO VEER TO THE LEFT AFTER TOUCHDOWN AND THE PILOT INITIATED A SECOND GO-AROUND. THE PILOT THEN ABORTED THE GO-AROUND, BUT WAS TOO LATE TO AVOID COLLIDING WITH A PARKED CESSNA 172.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82DA300
- Event ID
- 20020917X03607
- Case number
- LAX82DA300
- 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: ab6573b2ce927a8bec6641d29c05c61d4cf6627c21ad0fc03f8ef4218c6f2ffc; retrieved 2026-09-24T01:33:49.905Z.