NTSB CAROL · Event
Event CEN15IA337
Aircraft involved
Probable cause & findings
The gate lead/pushback driver's failure to recognize that the provisioning truck was within the safety zone of the gate during his walkaround due to distractions, which resulted in the subsequent collision between the airplane and the truck. Contributing to the collision was the provisioning truck driver's failure to recognize he was parked in the safety zone of an active gate adjacent to his assigned gate, and the guide agent's improper assumption that the safety zone was properly cleared by the gate lead/pushback driver.
Factual narrative
On August 4, 2015, about 1800 mountain daylight time, a Boeing 737-700 airplane, N779SW, sustained minor damage when it collided with a provisioning truck at Denver International Airport (DEN), Denver, Colorado. The flight crew and passengers on board the airplane were not injured. The driver in the service truck sustained minor injuries. The aircraft was registered to and operated by Southwest Airlines under the provisions of 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight. Visual meteorological conditions prevailed prior to and during the ground operations. The flight was originating at the time of the collision.The airplane was parked at Gate C28. A video of the event was provided to the investigator-in-charge by Southwest Airlines. The video started at a time stamp of 05:56:43 PM (MDT) on August 4, 2015. When the video started the provisioning truck was already parked on the far side of the airplane. The following is a timeline of the significant events captured by the video: 05:57:44 – Luggage belt pulls away from the right front side of the airplane 05:58:15 – The jet bridge starts to pull away from the airplane 05:58:36 – The gate lead appears to start his walk around 05:59:02 – The gate lead moves a safety cone from under the left wing and starts to walk towards the rear of the airplane (after this he is no longer visible to the camera) 05:59:29 – The gate lead is visible again under the empennage of the airplane 06:00:28 – The gate lead boards the airplane tug and the wing walker walks towards the right wing tip 06:00:53 – The Southwest Airlines (SWA) airplane scheduled for gate 26 arrives and starts to turn towards the gate 06:01:02 – The tug driver started to push the SWA airplane at gate 28 back as the SA airplane at gate 26 continued to pull in 06:01:17 – The collision between the airplane's left wing and the provisioning truck started 06:01:24 – The airplane stopped moving backwards and the truck stopped its roll The outboard trailing edge of the left wing collided with the fiberglass box on the passenger's side of the provisioning truck. The provisioning truck rolled and came to rest on the driver's side of the truck. The pushback driver immediately stopped the operations and the driver of the provisioning truck egressed from the truck without further incident. The trailing edge of the wing sustained minor impact damage to the skin, 2 inches in width and 18 inches in length. According to an interview with the lead agent/tug driver for gate 28, this was his first airplane of the day. He conducted a walk around the airplane but did not recall seeing the provisioning truck parked inside of the safety area. After understanding that he was cleared to push back by both the wing walker and the pilot, he started to push back. He stopped the push when he felt the tug or jerk of the airplane as it hit the provisioning truck. He commented that his headset was having issues. He also commented that he was stressed and potentially distracted by personal issues. In an interview with the guide agent, he stated that he did see the provisioning truck but it was not clear to him that it was in the safety area for gate 28. He assumed that it was clear and no issue as the lead agent/tug driver had walked passed it during his walk around and had subsequently announced that the walk around was complete. He was on the opposite side of the airplane during the pushback and commented that a second wing walker would have prevented this from happening. According to an interview with the provisions agent, he had parked outside of the safety area for gate 26 but acknowledged later that he was likely within the safety area for gate 28. He was awaiting an inbound airplane to service at gate 26. He also commented that he had never been told to remain clear of safety areas for adjacent gates, only to move his truck if he were asked. He did not receive such a request from the ground crew for gate 28. The Ground Operations Manual – 5.19.2 Pushback Procedures and Radio Communications and the Prepush Checklist (WN-1095 – REV. 11/12) for the pushback driver included an observation for the driver to ensure that the safety zone was clear of FOD, personnel, and equipment. The Provisioning Manual – Safety Section – 10.5 Driving and Ramp Safety 2.6.7 (Parking of Provisioning Vehicles Between Safety Zones – stated "Employees holding short at the gate for incoming aircraft should always make sure they are outside the safety zone. In addition, they should be aware of incoming flights that are to arrive at the adjacent gate and of flights that are pushing from an adjacent gate." During the pushback of a scheduled domestic passenger flight, the airplane's left wing collided with a provisioning truck, rolling the truck onto its side and resulting in minor damage to the airplane. The truck driver stated that he was waiting to service an inbound airplane at the adjacent gate and was likely parked within the safety zone of the incident airplane's gate. The gate lead/pushback driver for the incident airplane stated that he walked past the truck during the pre-pushback walk around but did not recall seeing the truck within the safety zone. The gate lead reported problems with his headset and personal life stress. It is likely that the gate lead was distracted by both during his walk around. Additionally, a guide agent positioned at the airplane's right wing stated that he saw the provisioning truck but assumed that it was not an issue since the gate lead had conducted a walkaround before pushback. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Ground crew - C
- C Personnel issues-Psychological-Attention/monitoring-Task monitoring/vigilance-Ground crew - C
- — Personnel issues-Task performance-Communication (personnel)-Lack of communication-Ground crew
- F Personnel issues-Psychological-Attention/monitoring-Attention-Ground crew - F
Verbatim from NTSB's published report. Source file
NTSB_2015_CEN15IA337.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Technical Memorandum (TM)
A preliminary study of a wake vortex encounter hazard boundary for a B737-100 airplane
A preliminary batch simulation study was conducted to define the wake decay required for a Boeing 737-100 airplane to safely encounter a Boeing 727 wake and land.
- NASA NTRS 2018 · Other
A Numerical Simulation Study to Develop an Acceptable Wake Encounter Boundary for a B737-100 Airplane
The National Aeronautics and Space Administration (NASA) is conducting research with the goal of enabling safe improvements in the capacity of the nation's air transportation system.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- arXiv 2023 · arXiv preprint
Radar detection of wake vortex behind the aircraft: the detection range problem
In this study, we showcased the detection of the wake vortex produced by a medium aircraft at distances exceeding 10 km using an X-band pulse-Doppler radar.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
Airline Pilot Risk Profiling by Using Unstable Approach Management Case
Risk and human decision-making cannot be separated from each other. Many of theories and studies have tried to analyze pilots’ decision-making processes, risk factors, and preference behavior in the a…
- Embry-Riddle Scholarly Commons 2023 · Journal article (IJAAA)
Historical Research and the case for a Fifth Component of SMS
Abstract Three tragic events from aviation history were examined using a Historical Research and Case Study Method. The events explored were the disasters of the Airship R101 (1930), the Space Shuttle…
Browse the full corpus — academia portal ↗