The U.S. aircraft register, updated daily
Accidents · NTSB DCA24LA034 · Final report

Boeing 717 incident near Kahului, Hawaii, November 30, 2023

On November 30, 2023 at about 4:14 pm local time, a 2004 Boeing 717, registered N494HA, suffered minor damage in an incident during taxi near Kahului, Hawaii (Kahului airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 119 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The captain did not verify that the tow tractor had exited the area in front of the airplane before taxiing for departure. Contributing factors were the dark conditions and the absence of an illuminated hazard beacon on the tow tractor, which reduced its conspicuity; the tow tractor operator’s positioning of the tractor too close to the airplane; the captain’s forgetting to verify the ramp agent’s display of the nosewheel bypass steering pin and provide him a return salute due to the performance of competing operational tasks; the flight crew’s rote performance of the “departure salute” checklist item and the required visual check of the sides of the airplane before commencing the taxi; and the ground crew’s discarding lighted wands during the pushback, which subsequently made it more difficult for them to attract the captain’s attention. In addition, the lack of procedure for ground crew to re-establish communications with the flight crew once the headset is disconnected from the airplane.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 30, 2023 · about 4:14 pm local time
Place
Kahului, Hawaii · Kahului · map
Type
Incident
Injuries
No one was hurt; 119 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Boeing 717 200, built 2004 · all 717s on the register
Registration
N494HA · registry record · serial 55182
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

After pushing back from the gate, Hawaiian Airlines (HAL) flight 105, a Boeing 717-200, collided with a tow tractor while the flight crew was initiating their taxi for departure from Kahului Airport (OGG), Maui, Hawaii. The 119 passengers and crew onboard were uninjured. One ramp worker sustained minor injuries. The airplane sustained minor damage. The flight crew reported that, after obtaining pushback clearance from air traffic control, they released the airplane’s brakes and the tow tractor operator began to push the airplane back from the gate. The captain reported that it was dark outside and raining. Due to an inoperative engine auto starter, the captain was required to perform the manual engine start procedure. After successfully starting the No. 1 (left) engine, the captain set the brakes and instructed the ground crew to disconnect the tow bar. The captain stated that he then began a manual start of the No. 2 (right) engine. After the No. 2 engine was started, he cleared the ground crew to disconnect the headset interphone and the nose landing gear bypass pin. The captain recalled that he saw one of the ramp agents (the escort) display the pin and its ribbon overhead with two hands. He recalled giving the escort a salute in return, but was unsure if the escort saw the salute. The first officer (FO) reported that he could not see the escort or the tow tractor from his position, as they were obscured by aircraft structure. He also stated that he was heads-down looking at the flight management system (FMS) and did not see whether the captain saluted the escort. The tow tractor operator recalled that the escort removed the steering bypass pin, disconnected the headset interphone cable from the airplane (thereby removing a means of direct communication with the flight crew), then stood near the passenger side of the tow tractor and displayed the pin for about two minutes. The escort reported that captains normally saluted him after he displayed the steering bypass pin, but he could not see the captain salute him on this occasion. He could see the captain moving around the cockpit and it appeared to him that the captain was performing instrument checks. The escort informed the tow tractor operator that he had not received a salute from the captain. The tow tractor operator recalled that she honked the horn to attempt to get the captain’s attention, then waved at the cockpit, but was unable to elicit a response from the captain. The flight crew’s after-start checklist included an item for “ground salute.” The FO stated that he did not know whether the captain provided the salute, but the captain did provide the proper response to the checklist callout. The FO requested and received a taxi clearance from air traffic control and the captain turned off the cockpit dome light in preparation for taxi. The tow tractor operator recalled that, upon seeing the cockpit light turn off, she realized that the airplane was about to taxi and informed the escort that they needed to leave the area. The escort began to run away from the airplane toward the gate, and the tow tractor operator put the tractor in gear and began to drive away from the airplane. Shortly after beginning the taxi, the crew felt an unusual motion as the airplane’s left main landing gear impacted the tow bar and the left wing impacted the tow tractor cab. When the captain was asked if he looked out the left side of the cockpit and said “clear left” in accordance with the airline’s flight operations manual (FOM) procedure, he stated, “I think I did say that…it was kind of dark out there. I don’t recall seeing anything on the left side.” Hawaiian Airlines Guidance During Pushback HAL Ground Service Manual (GSM) provided guidance regarding ground personnel duties and responsibilities during pushback procedures. The GSM stated that a control service agent was responsible for the pushback of the airplane, which included operating the tow tractor and communicating with the flight crew. Additionally, two wing walkers, equipped with illuminated wands for signaling during night operations, were required to be in position, with one of those assigned as escort. The escort was responsible for connecting the towbar and assisting with connecting the tow tractor to the airplane, removing the towbar, removing the steering bypass pin, and notifying the flight crew, by displaying the pin and its flag, that the pin had been removed and that the airplane was released for taxi. The GSM stated that, after removing the steering bypass pin and being cleared to disconnect the communication headset, the control service agent was to move the tractor and towbar out of the path of and facing away from the aircraft. The escort was to then ensure that personnel and equipment were in a safe area clear of the aircraft and await the “ready to taxi” signal (one flash of the airplane’s taxi light). Following the “ready to taxi” signal, the escort was to display the bypass pin flag, salute the flight crew, then board the tow tractor for transportation back to the terminal. The FOM stated that the escort should disconnect the steering bypass pin, display the pin flag, and “give the flight crew the procedure ending salute.” A separate table in the FOM stated that the escort should display the pin and issue a salute, and the flight crew should return the salute and flash the taxi light. Thus, the FOM contained conflicting information about the final communication. The captain stated that the procedure was for the escort to display the pin, the flight crew to provide a salute, and the escort to salute in return. He did not mention the flashing of the taxi light. When asked about the step in the FOM that involved flashing the taxi light, he said that he normally flashed the taxi light, but he forgot to do so during the incident pushback. Thus, the captain’s description of the procedure was not identical to any of the descriptions in the GSM or FOM. Regardless of the differences between the captain’s description and other available descriptions of the final communication procedure, the captain’s understanding was that he was supposed to see the escort’s display of the pin and acknowledge by providing a salute. In an interview, the captain stated that he did so; however, a variety of other evidence suggests that he did not. The escort did not recall seeing a salute from the captain, which is why he remained in position. The control service agent did not see the captain look in her direction or provide a salute when she was outside the tow tractor cab and trying to attract his attention. The FO was preoccupied with his own tasks, but he did not recall seeing the captain provide a salute. The cockpit voice recorder (CVR) recording did not capture the collision itself or the events preceding the incident, but did capture the flight crew’s conversation following the incident. The captain’s comments after the incident revealed concern that he had not provided the salute or was uncertain if he had provided the salute. The captain’s subsequent interview statement that he had provided a salute could have resulted from a contamination of his memory (due to the passage of time), or from concerns about disclosing potential noncompliance with a required procedure. Available evidence indicates it is most likely that the captain did not see the escort display the pin or provide a salute. Interviews with the flight crew indicated that they completed numerous operational tasks during the pushback and before beginning the taxi. Although multitasking is common during pushback, in this incident, the flight crew was required to complete two additional simultaneous tasks – the manual engine start procedure and reviewing/entering the load closeout information – which increased their cognitive loading and the likelihood of error. Neither crew member appeared to recognize how the demand on mental resources imposed by these additional tasks could impact their monitoring and awareness of the pushback procedures being conducted outside the airplane. The FOM gave flight crews some discretion regarding the load closeout, stating that when possible, it should be reviewed before taxi. If the load closeout was not received before completion of the after-start checklist, taxi to the departure runway was allowed; however, the review was required to be completed before takeoff. Both the departure salute and the “clear left” callout before initiating the taxi could have alerted the flight crew to the captain’s omitted visual confirmation of the removal of the steering bypass pin and the continued presence of the tow tractor. However, the evidence suggests that these procedural safeguards were likely performed in a rote fashion and without focused attention, which resulted in the presence of the tow tractor in the airplane’s taxi path to go undetected. While it is understandable that the flight crew chose to perform tasks related to the load closeout during the pushback in an attempt to increase efficiency, it is likely that this incident may have been avoided had the flight crew delayed their load closeout related tasks until after the pushback procedure was complete. Tow Tractor Lighting FAA guidance classifies pushback tractors as aircraft support vehicles and requires those that operate in the airport movement area to be equipped with a yellow flashing light mounted on the uppermost part of the vehicle structure. The yellow flashing light must be visible from any direction, day and night, including from the air. In addition, U.S. Department of Transportation Regulations pertaining to the state of Hawaii specify that, “Any vehicle proceeding onto the movement area between the hours of sunset and sunrise except those being escorted shall also operate an overhead flashing light which is visible for one mile.” The yellow flashing light is required to increase the conspicuity of ground vehicles in the airport movement area and to aid in their detection by flight crews and other vehicle operators. The tow tractor involved in this accident had a yellow flashing light mounted on its cab, as required. The tow tractor operator said that the light activated automatically when the tractor was “in motion” and deactivated when the tractor was “turned off.” They believed the light was illuminated during operation of the tow tractor. However, airport surveillance video revealed that the light was not illuminated during incident pushback. Further investigation revealed that the yellow light would only illuminate if the tow tractor’s ignition was on and the light’s rocker switch (located on the dash) was also switched on. The position of the rocker switch was not documented following the incident, and its position at the time of the incident could not be determined. It is likely that the tow tractor was inadvertently operated without the yellow flashing light illuminated, and that the absence of the light contributed to the captain overlooking the presence of the tow tractor as he began the taxi. Communications “Off Headset” Airport surveillance video and ramp agent interviews indicated that the escort and the tow tractor did not reposition away from the airplane’s path after the escort removed the communication cable and nosewheel bypass pin. The tow tractor remained about 10 feet from the side of the airplane’s fuselage, facing the left wing. The escort remained next to the tow tractor. The flight crew did not flash the airplane’s taxi light, and the escort did not wait for this signal to display the pin. The escort also discontinued use of his illuminated wands earlier during the pushback process, although the wands were required to be used for all signaling during night or low-visibility operations. The absence of the illuminated wand made the escort’s pin display less salient to the flight crew, and made it harder to attract the flight crew’s attention. Finally, the escort did not provide a final salute to the flight crew; thus, final communication attempts by the ramp crew were not conducted in accordance with procedures in the GSM. The GSM stated that, once “off headset,” the flight crew could re-establish communications with the ramp crew by flashing the taxi light three times; however, no such procedure was outlined for the ramp crew to re-establish communication with the flight crew after disconnecting the headset.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Ground collision during taxi defining event

The NTSB's findings

  • Environmental issues › Physical environment › Object/animal/substance › Ground equipment › Compliance w/ procedure
  • Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Ground crew
  • Personnel issues › Task performance › Use of equip/info › Use of checklist › Flight crew
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
  • Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
  • Personnel issues › Action/decision › Action › Incomplete action › Ground crew
  • Environmental issues › Physical environment › Object/animal/substance › Ground equipment › Effect on operation

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 3,616 hours in all; 575 in this make and model; 89 in the last 90 days; 47 in the last 30 days; 2,252 as pilot in command; 1,031 on instruments
  • Last flight review: September 14, 2023
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,863 hours in all; 233 in this make and model; 161 in the last 90 days; 62 in the last 30 days; 1,443 as pilot in command
  • Last flight review: August 2, 2023
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 32,839.4 hours
  • Last inspection: continuous airworthiness programme
  • Seats: 127
  • Landing gear: retractable
  • Engine 1: Rolls-Royc BR700-715A1-3 (turbofan); 25,881 hours total
  • Engine 2: Rolls-Royc BR700-715A1-3 (turbofan); 26,462 hours total
  • Operator: Hawaiian Airlines

The flight

  • Destination: Honolulu HI
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 280° at 5 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 11,000 ft
  • Temperature: 73°F (23°C), dew point 72°F (22°C)
  • Altimeter: 29.96 inHg
  • Observation at 5:54 am from PHOG

Weather report (METAR): PHOG 301554Z AUTO 28005KT 7SM BKN110 23/22 A2996 RMK AO2 SLP150 T02330222 TSNO

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
Passengers114

Documents from the investigation the NTSB's docket: the evidence folder behind the report

21 documents, released by the NTSB on February 24, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Flight Data Recorder Specialist's Factual Report PDF, 7 pages View Download
3 Flight Data Recorder - Attachment 1 (Tabular Data) data file Download
4 Operational Factors/human Performance Group - Factual Report PDF, 58 pages View Download
5 Operational Factors/human Performance - Attachment 1- Flight Crew Interview Transcripts PDF, 161 pages View Download
6 Operational Factors/human Performance - Attachment 2 - Maui Ground Personnel Interview Transcripts PDF, 178 pages View Download
7 Operational Factors/human Performance - Attachment 3 - FAA Personnel Interview Transcripts PDF, 130 pages View Download
8 Operational Factors/human Performance - Attachment 4 - Flight Crew Training Records [excerpts] PDF, 4 pages View Download
9 Operational Factors/human Performance - Attachment 5 - Flight Release PDF, 19 pages View Download
10 Operational Factors/human Performance - Attachment 6 - Hawaiian Airlines Minimum Equipment List - B-717 [excerpts] PDF, 3 pages View Download
11 Operational Factors/human Performance - Attachment 7 - Hawaiian Airlines Flight Crew Operations Manual [excerpts] PDF, 17 pages View Download
12 Operational Factors/human Performance - Attachment 8 - Hawaiian Airlines Flight Operations Manual [excerpts] PDF, 25 pages View Download
13 Operational Factors/human Performance - Attachment 9 - Hawaiian Airlines Ground Service Manuals [excerpts] PDF, 53 pages View Download
14 Operational Factors/human Performance - Attachment 10 - Hawaiian Airlines Operator Vehicle/gse Operator's Safety Check PDF, 3 pages View Download
15 Operational Factors/human Performance - Attachment 11 - Accident Flight Acars Load Closeout PDF, 2 pages View Download
16 Operational Factors/human Performance - Attachment 12 - Archived Notams PDF, 5 pages View Download
17 Operational Factors/human Performance - Attachment 13 - Night Ground Handling Observations at Kahului Airport PDF, 25 pages View Download
18 Operational Factors/human Performance - Attachment 14 - Security Camera ASF file Download
19 Operational Factors/human Performance - Attachment 15 - Security Camera Video Hal Gates 17-19 ASF file Download
20 Statement of Party Representatives to NTSB Investigation PDF, 21 pages View Download
21 Cockpit Voice Recorder - Specialista��s Factual Report PDF, 6 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.