LAX82DA223 · Robinson R22
Navajo Aviation Robinson R22 · Accident: in flight collision with terrain/water during landing
From Buchanan Field (CCR) to Buchanan Field (CCR)
Event
- NTSB case
- LAX82DA223
- 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
Robinson R22
- Aircraft type
- Robinson R22
- Category
- Helicopter
- 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
- N90165
- Operator
- Navajo Aviation
- Onboard fatalities
- Unknown
- Route
- From Buchanan Field (CCR), Concord, CATo Buchanan Field (CCR), Concord, 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 · 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
- In flight collision with terrain/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 › Compensation for wind conditions, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A LANDING, THE PILOT REPORTED THAT HE CAME TO A 3 FT HOVER THEN INITIATED A DESCENT BY LOWERING THE COLLECTIVE. HE STATED THAT WHEN THE HELICOPTER WAS ABOUT 6 INCHES ABOVE THE GROUND, HE LOWERED THE COLLECTIVE TO COMPLETE THE LANDING, AND AT THAT POINT, A GUST OF WIND ROCKED THE HELICOPTER REARWARD. THE REAR PART OF THE RIGHT SKID STRUCK THE GROUND. THE PILOT REPORTED THAT AT ABOUT THAT TIME, HE HEARD AND FELT A SLIGHT THUMP AND EVERYTHING STARTED SPINNING. SUBSEQUENTLY, THE HELICOPTER WAS STOPPED ON THE GROUND AND SHUTDOWN. AFTER THE ACCIDENT, AN EXAMINATION REVEALED THAT A TAIL ROTOR BLADE, THE LOWER HALF OF THE VERTICAL FIN AND THE TAIL ROTOR SKID HAD BROKEN. THE PREVAILING WIND WAS FROM 280 DEGREES AT 12 KNOTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82DA223
- Event ID
- 20020917X03565
- Case number
- LAX82DA223
- 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: e2d18c659c3501be394eaab23b7efb0bb5fa6fa94842f55b23268a4eff90785e; retrieved 2026-09-24T02:58:43.127Z.