FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Papillon Airways Eurocopter EC 130 B4 accident

25 Jul 2014 · Boulder City, NV, United States

Eurocopter EC 130 B4 and Grand Canyon Airlines de Havilland DHC 6 300 310 · Accident: ground collision during landing

Report a problem

Event

NTSB case
WPR14LA313
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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Eurocopter EC 130 B4

Aircraft type
Eurocopter EC-130
Category
Helicopter
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
N154GC
Onboard fatalities
Unknown
Route
From Boulder City Municipal Airport (BVU), Boulder City, NVTo Boulder City Municipal Airport (BVU), Boulder City, NV
Aircraft age
About 4 years (built 2010)
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 135: Air Taxi & Commuter
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
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
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · de Havilland DHC 6 300 310

Aircraft type
de Havilland DHC-6
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
N190GC
Onboard fatalities
Unknown
Route
From Boulder City Municipal Airport (BVU), Boulder City, NVTo not recorded
Aircraft age
About 44 years (built 1970)
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 135: Air Taxi & Commuter
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
Taxi · to runway
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
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial helicopter pilot was operating on his first day of revenue service for the aerial tour company and was returning to the nontowered airport at the completion of a tour with six passengers. The pilot complied with the published arrival procedures, including flying the prescribed route and making the appropriate radio position callouts on the airport's common traffic advisory frequency (CTAF). Concurrent with the helicopter's arrival, the captain and first officer of an aerial tour airplane were beginning the taxi-out for departure of the positioning flight. The airport arrival procedures, layout, and wind conditions resulted in the two aircraft having to use the same portion of taxiway Delta, in the same direction, for their respective operations.

The helicopter pilot reported that he first saw the airplane when the helicopter was turning westbound and descending over Delta; at that time, the airplane was taxiing southbound on the ramp toward Delta. The helicopter pilot announced his location and intentions and continued descending along Delta. When the airplane reached Delta, the first officer announced on the CTAF that the airplane was planning to proceed westbound on Delta. The captain reported that he looked but did not see any helicopters and that he then proceeded to turn westbound onto Delta, which placed the airplane directly into and under the helicopter's flightpath and prompted the helicopter pilot to radio that he was "right above" the airplane and repeat his landing intentions. The helicopter pilot continued the descent based on his hearing a "double-click" on the CTAF, which he interpreted as the airplane flight crew's acknowledgement that they saw and would avoid the helicopter. Shortly thereafter, the helicopter collided with the airplane; damage patterns indicated that the two aircraft were aligned in nearly the same direction (westbound) at the time of impact.

Because the helicopter was approaching from the airplane's left, along taxiway Delta, and was close in, it should have been readily visually detectable by the captain. Given that the first officer was aware of the inbound helicopter and should have been aware of its location and intentions based on the radio calls, the airplane's flight crew should have recognized the high potential for conflict and operated the airplane in a manner to ensure that a collision would not occur. In addition, the helicopter, as the landing aircraft, had the right of way over the departing airplane. The simplest and most effective method to prevent any conflict would have been for the airplane flight crew to stop on the ramp and not proceed onto taxiway Delta until the helicopter was positively determined to no longer pose a collision threat. However, there was no evidence that the airplane stopped before it turned from the ramp onto taxiway Delta. The evidence indicated that the airplane taxied out just ahead of and below the descending but faster moving helicopter, which significantly reduced the helicopter pilot's ability to avoid the airplane.

Probable cause

The airplane flight crew’s failure to exercise the necessary vigilance and precautions and yield the right of way to the landing helicopter, which resulted in the airplane colliding with the helicopter. Contributing to the accident was the helicopter pilot’s decision to continue his descent without positively determining that the airplane did not pose a collision hazard.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14LA313
Event ID
20140726X45400
Case number
WPR14LA313
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: 4c388502c83a8bbbea1ad252645374a1a4e3603c17bf2376293ac8a67b1d80ed; retrieved 2026-09-13T18:23:14.828Z.