GAA17CA365 · Beech 58 UNDESIGNAT
Beech 58 UNDESIGNAT · Accident: collision during takeoff/landing
From an unrecorded airport to Ingleside Regional Airport (TFP)
Event
- NTSB case
- GAA17CA365
- 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
- Instrument Meteorological Cond
Beech 58 UNDESIGNAT
- Aircraft type
- Beechcraft 58
- 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
- N58SM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Ingleside Regional Airport (TFP), Ingleside, TX
- Aircraft age
- About 41 years (built 1976)
- 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
- 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
- Destroyed
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the twin-engine airplane reported that, while on a visual approach for landing, he transmitted the appropriate radio calls and noted that all the airplane lights were illuminated. He added that the airplane touched down about 400 ft down the runway, at which time he noticed a truck approaching the runway from the south. The pilot observed the truck hesitate and then cross the runway towing a large trailer with a tractor loaded on the back. The pilot swerved the airplane to the left to avoid impacting the trailer, but the right wing impacted the trailer. The pilot reported that, after the collision, the truck driver apologized and stated that he thought he could "beat" the airplane across the runway.
The truck driver reported that he looked both ways down the runway and did not observe any aircraft. He added that, while he was crossing, he saw an airplane. He accelerated the truck, but the airplane impacted the end of the trailer.
The airport manager reported that the truck driver was not one of the airport's employees but had volunteered, without compensation, to cut and bale hay at the far corner of the airport. He added that all weather station or other repair technicians are escorted to their location by airport staff. He also reported that this was the first time that he had allowed the truck driver to cut hay on the airfield and that he had thoroughly briefed the driver to stay 50 ft away from the runway. The driver reported to the airport manager that he took the quicker and drier route instead of taking the longer and safer route because he was concerned with getting his truck and trailer stuck in an area that was known to be more saturated after the previous night's precipitation.
After the collision, the airplane was destroyed by postimpact fire.
In an effort to improve safety, the Precinct 4 Commissioner created a standard operating procedure that encompassed operating procedures, training curriculum, and a training manual that was derived from Advisory Circular 150/5210-20 Change 1.
Probable cause
The pilot’s inability to avoid a collision with an unauthorized vehicle on the runway during the landing roll and the truck driver’s decision to cross the runway in front of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA365
- Event ID
- 20170626X22152
- Case number
- GAA17CA365
- 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. 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: 9b65f149a2a833e1ae4a6fa6938117c5a33d4a95a6733e3a67e9d25f4da60841; retrieved 2026-09-16T05:27:39.109Z.