# NTSB GAA17CA365: Beech 58, N58SM, Ingleside, TX, June 26, 2017 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: June 26, 2017, 10:45 local (15:45 UTC) - Place: Ingleside, TX - Coordinates: 27.91361, -97.211944 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=27.9136&lon=-97.2119&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report March 27, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 95437 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA365 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95437/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95437 - Page: https://openairdocs.org/ntsb/GAA17CA365 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action selection](https://openairdocs.org/ntsb-findings/02041010): Personnel issues › Action/decision · Other (probable cause); cases with it: [Beech 58, 4 cases](https://openairdocs.org/ntsb-findings/02041010/cases.md?model=1152740), [All aircraft, 397 cases](https://openairdocs.org/ntsb-findings/02041010/cases.md) - [Object/animal/substance: ground vehicle](https://openairdocs.org/ntsb-findings/03022025): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Beech 58, 1 case](https://openairdocs.org/ntsb-findings/03022025/cases.md?model=1152740), [All aircraft, 132 cases](https://openairdocs.org/ntsb-findings/03022025/cases.md) - [Policy/procedure: availability of policy/proc](https://openairdocs.org/ntsb-findings/04021010): Organizational issues › Management · Airport; cases with it: [Beech 58, 1 case](https://openairdocs.org/ntsb-findings/04021010/cases.md?model=1152740), [All aircraft, 28 cases](https://openairdocs.org/ntsb-findings/04021010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Beech 58, 3 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=1152740), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Post-impact: Fire/smoke (post-impact)](https://openairdocs.org/ntsb-events/170); cases with it: [Beech 58, 3 cases](https://openairdocs.org/ntsb-events/170/sequence.md?model=1152740), [All aircraft, 354 cases](https://openairdocs.org/ntsb-events/170/sequence.md) ## Analysis 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. ## Factual 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. ## Aircraft - Registration: [N58SM](https://openairdocs.org/deregistered/N58SM-2019-12-30), registration cancelled 2019-12-30, S/N TK-8, built 1976 (OpenAirDocs) - Reported make and model: BEECH 58 (UNDESIGNAT) - Registry model: [Beech 58](https://openairdocs.org/model/beech-58) (registry code 1152740) (OpenAirDocs) - Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: TK-8 - Year built: 1976 - Engines: CONT MOTOR TSIO-520 SER reciprocating; CONT MOTOR TSIO-520 SER reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Destination: TFP, Ingleside, TX - Flight plan: Unknown - Airport: TFP, Mccampbell-Porter, runway 31, 5,000 × 75 ft, asphalt - Equipment: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: minor; airline transport, commercial, flight engineer; airplane ratings: single-engine sea, multi-engine land, single-engine land; medical: class 1, with waivers/limitations ## Weather - Conditions: Instrument (IMC), Day - Wind: calm - Temperature: 86 °F, dew point 75 °F - Altimeter: 30.05 inHg - Observed at: KTFP, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20170626024629A](https://openairdocs.org/incident/20170626024629A), Jun 26, 2017: Beech 58, Aransas Pass, TX, Destroyed. On June 26, 2017, airman arrived at Mccampbell-Porter Airport from the south. The approach and landing on runway 31 were uneventful. As the airman was letting… ## Docket (6 files) The files NTSB released with the investigation on March 5, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95437. 1.1 MB in all. - Record of Email - Bart Burns (Airplane Pilot) (item 1, .PDF, 112 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460533&FileExtension=.PDF&FileName=Record%20of%20Email%20-%20Bart%20Burns%20(Airplane%20Pilot)-Master.PDF - Donald Young (Driver) Statement (item 2, .PDF, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460511&FileExtension=.PDF&FileName=Donald%20Young%20(Driver)%20Statement-Master.PDF - Justin Hintz (FBO Manager) Statement (item 3, .PDF, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460512&FileExtension=.PDF&FileName=Justin%20Hintz%20(FBO%20Manager)%20Statement-Master.PDF - Paul L (Airport Manager) Statement (item 4, .PDF, 245 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460513&FileExtension=.PDF&FileName=Paul%20L%20(Airport%20Manager)%20Statement-Master.PDF - Record of Email(Airport Tenant) (item 5, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460534&FileExtension=.PDF&FileName=Record%20of%20Email(Airport%20Tenant)-Master.PDF - Accident Photos (Courtesy of FAA) (item 6, .PDF, 2 photos, 482 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460514&FileExtension=.PDF&FileName=Accident%20Photos%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.