20260430009649I

Incident · No damage

FAA incident report · Dehavilland DHC-6-300 · Tusayan, AZ · April 30, 2026

Date
April 30, 2026 · 14:42 local
Place
Tusayan, AZ
Airport
Grand Canyon National Park Air
Phase of flight
Landing: Rollout
Operating rules
Air taxi and commuter (Part 135)
Operator
GCNA
Damage
No damage
Aircraft
N190GC
Reported as
Dehavilland DHC-6-300
Reported engine
Pratt & Whitney Canada PT6A-27
People aboard
15
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
Pilot’s flight hours
5,760 total972 in this make and model50 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On April 30, 2026, at 2142Z (14:42 MST local), a de-havilland DHC-6-300, was involved in a runway excursion event at Grand Canyon National park airport (kgcn), Tusayan, AZ. The aircraft was not damaged. Thirteen passengers and two pilots were not injured. The aircraft was operated as a 14 CFR part 135 on-demand commercial air tour flight.

The flight departed at 14:07 MST from kgcn on a 45 minute on-demand sightseeing air tour flight of Grand Canyon with a return destination of kgcn.

Kgcn is an airport on the south rim of Grand Canyon located at an elevation of 6,600 ft mean sea level (MSL), surrounded by tall pine trees and shrubs. It has a single, 8,999 ft long by 150 ft wide 030/210 degree-oriented runway. The reported weather at kgcn at the time of the landing incident was fair, temperature 63F, wind variable @ 7MPH gusting 20MPH, baro 23.42IN.

The pilots received landing weather via kgcn ATIS and cleared to land on runway 3 with the second-in-command (SIC) as pilot flying.

The pilot-in-command (PIC) reported that the final approach was stable, on speed, on centerline, and although gusting winds were causing changes in air speed, they were not enough to require large changes in engine power. The SIC was maintaining a crab angle while the airplane was on final.

The PIC reported that shortly after touchdown, the first officer began to lose directional control when the nosewheel contacted the runway. The PIC assumed control of the aircraft and shortly began to lose directional control. The aircraft swerved to the left and exited the runway environment approximately mid-field. The aircraft stopped approximately 75’ feet off the left side of the runway.

On may 1, 2026, the operator provided the following statements from the PIC and SIC:

PIC statement: “ioe flight. As, pilot monitoring, when aircraft veered to the left, I called "my controls." I arrested the swerve but was unable to keep the aircraft from exiting the runway.”

SIC statement: “coming into land. Had a crosswind from the left and was centered coming into land. Landed and gust from the right happened aggressively and pushed us left and I went right rudder but unable to bring the airplane back to centerline and kept going left towards off the runway. Captain xxx took control immediately and slowed us down with brakes and reverse thrust. It was off the runway about 50 ft if I remember correctly. Tower asked if we could taxi off or need to be towed and captain xxx responded we would try to taxi. No engines were shut down and we checked the wheels and outside of the aircraft and they were fine and taxied back to the ramp. All pax said they were okay and we apologized profusely.”

On may 1, 2026, the operator provided photographs of the aircraft tire/skid marks on the runway and when the aircraft departed the runway edge. No airport property was damaged because of the runway excursion incident.

Root cause analysis: the PIC failed to maintain directional control of the aircraft during gusty crosswind landing conditions.

On may 4, 2026, the operator’s director of operations (do) stated the PIC was terminated from employment and that they will be conducting re-training of the SIC regarding crosswind landings, use of asymmetrical power and asymmetrical reverse thrust in strong gusty wind conditions to address this incident and previous accident and incidents with the intent to mitigate future accidents. The do stated that their maintenance department concluded that there were no mechanical issues with the aircraft and full flight control continuity was established during the post-incident aircraft inspection.

As the FAA filed it

ON APRIL 30, 2026, AT 2142Z (14:42 MST LOCAL), A DE-HAVILLAND DHC-6-300, WAS INVOLVED IN A RUNWAY EXCURSION EVENT AT GRAND CANYON NATIONAL PARK AIRPORT (KGCN), TUSAYAN, AZ. THE AIRCRAFT WAS NOT DAMAGED. THIRTEEN PASSENGERS AND TWO PILOTS WERE NOT INJURED. THE AIRCRAFT WAS OPERATED AS A 14 CFR PART 135 ON-DEMAND COMMERCIAL AIR TOUR FLIGHT.

THE FLIGHT DEPARTED AT 14:07 MST FROM KGCN ON A 45 MINUTE ON-DEMAND SIGHTSEEING AIR TOUR FLIGHT OF GRAND CANYON WITH A RETURN DESTINATION OF KGCN.

KGCN IS AN AIRPORT ON THE SOUTH RIM OF GRAND CANYON LOCATED AT AN ELEVATION OF 6,600 FT MEAN SEA LEVEL (MSL), SURROUNDED BY TALL PINE TREES AND SHRUBS. IT HAS A SINGLE, 8,999 FT LONG BY 150 FT WIDE 030/210 DEGREE-ORIENTED RUNWAY. THE REPORTED WEATHER AT KGCN AT THE TIME OF THE LANDING INCIDENT WAS FAIR, TEMPERATURE 63F, WIND VARIABLE @ 7MPH GUSTING 20MPH, BARO 23.42IN.

THE PILOTS RECEIVED LANDING WEATHER VIA KGCN ATIS AND CLEARED TO LAND ON RUNWAY 3 WITH THE SECOND-IN-COMMAND (SIC) AS PILOT FLYING.

THE PILOT-IN-COMMAND (PIC) REPORTED THAT THE FINAL APPROACH WAS STABLE, ON SPEED, ON CENTERLINE, AND ALTHOUGH GUSTING WINDS WERE CAUSING CHANGES IN AIR SPEED, THEY WERE NOT ENOUGH TO REQUIRE LARGE CHANGES IN ENGINE POWER. THE SIC WAS MAINTAINING A CRAB ANGLE WHILE THE AIRPLANE WAS ON FINAL.

THE PIC REPORTED THAT SHORTLY AFTER TOUCHDOWN, THE FIRST OFFICER BEGAN TO LOSE DIRECTIONAL CONTROL WHEN THE NOSEWHEEL CONTACTED THE RUNWAY. THE PIC ASSUMED CONTROL OF THE AIRCRAFT AND SHORTLY BEGAN TO LOSE DIRECTIONAL CONTROL. THE AIRCRAFT SWERVED TO THE LEFT AND EXITED THE RUNWAY ENVIRONMENT APPROXIMATELY MID-FIELD. THE AIRCRAFT STOPPED APPROXIMATELY 75’ FEET OFF THE LEFT SIDE OF THE RUNWAY.

ON MAY 1, 2026, THE OPERATOR PROVIDED THE FOLLOWING STATEMENTS FROM THE PIC AND SIC:

PIC STATEMENT: “IOE FLIGHT. AS, PILOT MONITORING, WHEN AIRCRAFT VEERED TO THE LEFT, I CALLED "MY CONTROLS." I ARRESTED THE SWERVE BUT WAS UNABLE TO KEEP THE AIRCRAFT FROM EXITING THE RUNWAY.”

SIC STATEMENT: “COMING INTO LAND. HAD A CROSSWIND FROM THE LEFT AND WAS CENTERED COMING INTO LAND. LANDED AND GUST FROM THE RIGHT HAPPENED AGGRESSIVELY AND PUSHED US LEFT AND I WENT RIGHT RUDDER BUT UNABLE TO BRING THE AIRPLANE BACK TO CENTERLINE AND KEPT GOING LEFT TOWARDS OFF THE RUNWAY. CAPTAIN XXX TOOK CONTROL IMMEDIATELY AND SLOWED US DOWN WITH BRAKES AND REVERSE THRUST. IT WAS OFF THE RUNWAY ABOUT 50 FT IF I REMEMBER CORRECTLY. TOWER ASKED IF WE COULD TAXI OFF OR NEED TO BE TOWED AND CAPTAIN XXX RESPONDED WE WOULD TRY TO TAXI. NO ENGINES WERE SHUT DOWN AND WE CHECKED THE WHEELS AND OUTSIDE OF THE AIRCRAFT AND THEY WERE FINE AND TAXIED BACK TO THE RAMP. ALL PAX SAID THEY WERE OKAY AND WE APOLOGIZED PROFUSELY.”

ON MAY 1, 2026, THE OPERATOR PROVIDED PHOTOGRAPHS OF THE AIRCRAFT TIRE/SKID MARKS ON THE RUNWAY AND WHEN THE AIRCRAFT DEPARTED THE RUNWAY EDGE. NO AIRPORT PROPERTY WAS DAMAGED BECAUSE OF THE RUNWAY EXCURSION INCIDENT.

ROOT CAUSE ANALYSIS: THE PIC FAILED TO MAINTAIN DIRECTIONAL CONTROL OF THE AIRCRAFT DURING GUSTY CROSSWIND LANDING CONDITIONS.

ON MAY 4, 2026, THE OPERATOR’S DIRECTOR OF OPERATIONS (DO) STATED THE PIC WAS TERMINATED FROM EMPLOYMENT AND THAT THEY WILL BE CONDUCTING RE-TRAINING OF THE SIC REGARDING CROSSWIND LANDINGS, USE OF ASYMMETRICAL POWER AND ASYMMETRICAL REVERSE THRUST IN STRONG GUSTY WIND CONDITIONS TO ADDRESS THIS INCIDENT AND PREVIOUS ACCIDENT AND INCIDENTS WITH THE INTENT TO MITIGATE FUTURE ACCIDENTS. THE DO STATED THAT THEIR MAINTENANCE DEPARTMENT CONCLUDED THAT THERE WERE NO MECHANICAL ISSUES WITH THE AIRCRAFT AND FULL FLIGHT CONTROL CONTINUITY WAS ESTABLISHED DURING THE POST-INCIDENT AIRCRAFT INSPECTION.

Other reports on N190GC · 1

Matched to the same aircraft by N-number and date.