FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX83LA222 · Grumman 164B

7 May 1983 · Lodi, CA, United States

Grumman 164B · Accident: on ground/water collision with object during takeoff

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
LAX83LA222
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

Grumman 164B Possible conflict

Aircraft type
Grumman 164
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
N6530K
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Takeoff
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
On ground/water collision with object
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Visual lookout, inadequate
  • Pilot of other aircraft › Visual lookout, inadequate

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

NTSB narrative

THE AIRCRAFT WAS ROLLING FOR TAKEOFF AT DAWN WHEN IT COLLIDED WITH ANOTHER CROP DUSTER TAXIING IN THE OPPOSITE DIRECTIONTHE AIRCRAFT TAKING OFF HAD ROLLED ABOUT 100 FEET WHEN THE PILOT SAW A RED LIGHT ON THE RUNWAY AND ABORTED THE TAKEOFF AND ATTEMPTED TO STOP OR EVADE THE LIGHT. ALL EFFORTS TO TURN OR STOP WERE NOT SUCCESSFUL IN AVOIDING A COLLISION AND ATAN ESTIMATED 5 MPH UNDER HEAVY BRAKING THE AIRCRAFT NOSED DOWN AND COLLIDED AT THE SAME TIME. THE FUEL TANKS OF BOTH AIRCRAFT RUPTURED AND FIRE ERUPTED IMMEDIATELY. THE TAXIING CROP DUSTER WAS NOT BEING OPERATED INCIDENT TO FLIGHT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX83LA222
Event ID
20001214X43039
Case number
LAX83LA222
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: 9d87ff22e17163c5b57594d379f1b695f818889cdf24ff2a262db389ecb28fb5; retrieved 2026-09-23T22:17:46.990Z.