CEN23LA197 · Gulfstream-Schweizer A/C Corp GULFSTREAM AM G-164B
Vincent Flying Service Gulfstream-Schweizer A/C Corp GULFSTREAM AM G-164B and Vincent Flying Service Gulfstream-Schweizer A/C Corp GULFSTREAM AM G-164D · Accident: collision during takeoff/landing
Event
- NTSB case
- CEN23LA197
- 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
- Event fatalities
- Unknown
- 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
Aircraft 1 · Gulfstream-Schweizer A/C Corp GULFSTREAM AM G-164B
- Aircraft type
- Gulfstream Schweizer A/c GULFSTREAM AM G-164B
- 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
- N8337K
- Operator
- Vincent Flying Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 43 years (built 1980)
- 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 137: Agricultural
- 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
- 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
- Collision during takeoff/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
Aircraft 2 · Gulfstream-Schweizer A/C Corp GULFSTREAM AM G-164D
- Aircraft type
- Gulfstream Schweizer A/c GULFSTREAM AM G-164D
- 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
- N8331K
- Operator
- Vincent Flying Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 43 years (built 1980)
- 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 137: Agricultural
- 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
- 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
- Collision during takeoff/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
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The two airplanes were conducting agricultural operations at a private airstrip. The pilot of the landing airplane reported that, while airborne, he noticed the departing airplane was being loaded at the tender truck. The pilot of the landing airplane estimated that he would have enough time to land and clear the runway before the departing airplane was finished loading. The pilot of the departing airplane reported that after loading, he positioned his airplane on the runway and began his takeoff roll. Meanwhile, the pilot of the landing airplane touched down in the opposite direction of the departing airplane. The pilot of the landing airplane reported that while he was slowing down on the landing roll, he looked over his airplane’s hopper and noticed the departing airplane rolling toward him. The pilot of the landing airplane attempted to veer out of the way of the departing airplane but was unsuccessful. The left wing of the landing airplane struck the left wing of the departing airplane. The landing airplane sustained substantial damage to both left wings, the fuselage, the horizontal stabilizer, and the elevator. The departing airplane sustained substantial damage to all four wings and the fuselage. Both pilots reported that there were no preimpact mechanical failures or malfunctions with the airplanes that would have precluded normal operation. Both pilots reported that neither made a radio call announcing their intentions.
Probable cause
The failure of both pilots to see and avoid each other resulting in a collision on the airstrip. Contributing was the pilots’ failure to announce their intentions over their radios as they were taking off and landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA197
- Event ID
- 20230522192225
- Case number
- CEN23LA197
- 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, cause areas. 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: e05c610521b1cc964827d93d8c5d78e1c38127cf4f48b283ef8cd5b7d3713f0b; retrieved 2026-09-13T18:41:28.147Z.