Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 26, 2017 · Beech 58 Undesignat · N58SM

Ingleside, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 26, 2017
Injury Outcomes
1 injury (1 minor injury)
Location
Ingleside, TX
Aircraft
Beech 58 Undesignat (1976)
Tail Number
N58SM
Injuries
Minor
Aircraft Damage
Destroyed
NTSB Number
GAA17CA365

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.

NTSB 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.

Full 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 vehicle approaching the runway from the south side. The pilot observed the vehicle hesitate, 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 head on. The pilot was unable to avoid the vehicle, and the right wing impacted the trailer. The pilot reported that after the collision, the driver of the truck apologized, and stated that he thought he could beat the airplane across the runway. The driver of the vehicle 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 vehicle, but the airplane impacted the end of the trailer. The airport manager reported that the driver of the vehicle was not one of the airports 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 driver of the vehicle 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, opposed to 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. A witness located at the airport reported that he observed the vehicle cross the center of the runway four times, with a truck and trailer, and two times while driving a tractor with a cutter attached. He noted that the driver of the tractor was traveling more than safe speed around the hanger areas. After the collision, the airplane was destroyed during the post-impact fire. In an effort to improve safety, the Precinct 4 Commissioner created a Standard Operating Procedure (SOP) that encompassed operating procedures, training curriculum, and a training manual that was derived from Advisory Circular (AC) 150/5210-20 Change 1.

Flight

Event TypeAccident
Event Time10:45 CDT
Nearest AirportMccampbell-Porter (0nm NW)
Runway31
Runway Length5000 ft
Runway Width75 ft
Flight Plan FiledUnknown
Flight Plan ActivatedUnknown
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftBeech 58 Undesignat
Tail NumberN58SM
Aircraft CategoryAir
DamageDestroyed
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsCont Motor · TSIO-520 SER · Reciprocating | Cont Motor · TSIO-520 SER · Reciprocating
Seats6

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 65 · First Class · Minor

Conditions

ConditionsIMC
LightDaylight
WindCalm
CeilingNone
Altimeter30.05 inHg
Observation Time15:15
Weather SourceWFAC

Appendix: Source Data