Incident Overview

Date: Friday 28 June 2024
Aircraft Type: Bombardier DHC-8-402Q Dash 8
Owner/operator: Porter Airlines
Registration Number: C-GLQP
Location: Fredericton Airport, NB (YFC/CYFC) – ÿ Canada
Phase of Flight: Landing
Status: Substantial
Casualties: Fatalities: 0 / Occupants: 78
Component Affected: The aircraft’s control surfaces, particularly the ailerons and rudder, and the flight control system, were directly impacted by the excessive control adjustments and subsequent bounce.The aircraft’s control surfaces, particularly the ailerons and rudder, and the flight control system, were directly impacted by the excessive control adjustments and subsequent bounce.
Investigating Agency: TSBTSB
Category: Accident
On October 26, 2023, a Porter Airlines DHC-8-402Q flight PD2375 experienced a tailstrike during touchdown on Runway 27 at Fredericton Airport, NB (YFC). The flight crew initiated a go-around after a brief contact with the runway, resulting in a subsequent second contact. The aircraft’s approach speed was adjusted to ensure a safe landing. The pilot, operating at cruise altitude, adjusted the approach speed to minimize the landing weight and flaps setting. A 10-knot buffer was added to the planned approach speed, resulting in a planned approach speed of 134 KIAS. The descent rate was increased to 980 fpm, and the pitch was adjusted to 1.1ø to 6.8ø. The aircraft experienced a series of maneuvers, including a bounce and a vertical acceleration, before the runway contact. The pilot initiated a go-around, and subsequent contact with the runway resulted in a second vertical acceleration of 1.42 g. The flight crew reported the lights illuminating and the master warning lights flashing. The incident was resolved through a visual flight rules circuit and return to landing.On October 26, 2023, a Porter Airlines DHC-8-402Q flight PD2375 experienced a tailstrike during touchdown on Runway 27 at Fredericton Airport, NB (YFC). The flight crew initiated a go-around after a brief contact with the runway, resulting in a subsequent second contact. The aircraft’s approach speed was adjusted to ensure a safe landing. The pilot, operating at cruise altitude, adjusted the approach speed to minimize the landing weight and flaps setting. A 10-knot buffer was added to the planned approach speed, resulting in a planned approach speed of 134 KIAS. The descent rate was increased to 980 fpm, and the pitch was adjusted to 1.1ø to 6.8ø. The aircraft experienced a series of maneuvers, including a bounce and a vertical acceleration, before the runway contact. The pilot initiated a go-around, and subsequent contact with the runway resulted in a second vertical acceleration of 1.42 g. The flight crew reported the lights illuminating and the master warning lights flashing. The incident was resolved through a visual flight rules circuit and return to landing.

Description

Porter Airlines flight PD2375, a DHC-8-402Q, suffered a tailstrike during touchdown on runway 27 at Fredericton Airport, NB (YFC). While at cruise altitude, the Pilot Flying (the captain) briefed the area navigation global navigation satellite system (RNAV [GNSS]) Z approach to Runway 27. Based on the landing weight and the flaps set at 15ø, the planned target landing reference speed (VREF) was 124 knots indicated airspeed (KIAS), and the flight crew added a 10-knot buffer, increasing the planned approach speed to 134 KIAS. At 1356, the flight was cleared to land, and the control tower reported the winds to be from 350ø magnetic at 11 knots. At 13:59:30, when the aircraft was 267 feet above touchdown zone elevation (TDZE), the PF disconnected the autopilot and began to fly the approach manually. When the aircraft was 135 feet above the TDZE, the aircraft was travelling at 126 KIAS, the descent rate was 700 fpm, and the pitch was 3.2ø. When the aircraft was 20 feet above the TDZE, it was travelling at 124 KIAS, the descent rate had increased to 980 fpm, and the pitch was 1.1ø. The headwind component decreased from 5.5 knots to 0.5 knots within 3 seconds, increasing the maximum descent rate to 1050 fpm. In response, over a period of 2 seconds, the PF increased the pitch from 1.1ø to 6.8ø. The power was consistently at 14% torque. At 13:59:53, the right main landing gear contacted the runway, followed by the left main landing gear. A vertical acceleration of 3.51 g was recorded. After the initial contact with the runway, the aircraft bounced, and the flight crew initiated a go-around in accordance with Porter Airlines? standard operating procedures (SOPs). Two seconds later, a second runway contact occurred with a recorded vertical acceleration of 1.42 g. After the first touchdown, the TOUCHED RUNWAY warning light illuminated, indicating that a sensor near the tail section of the aircraft had been triggered by contact with the runway surface. In addition, the master warning light started flashing. During the climbout, the flight crew noticed the master warning and TOUCHED RUNWAY warning lights; however, they did not discuss the issue further at that time. The flight crew were cleared by the tower controller to conduct a visual flight rules circuit and return to land. The aircraft landed uneventfully at 1408, and the flight crew taxied the aircraft to the apron and shut it down. Damage to the lower portion of the aft fuselage section was identified and company flight operations personnel were notified.

Source of Information

https://www.reddit.com/r/rampagent/comments/1dqps00/just_witnessed_my_first_q400_tail_strike_at_work/, https://www.flightradar24.com/data/aircraft/c-glqp#35e5e56ahttps://www.reddit.com/r/rampagent/comments/1dqps00/just_witnessed_my_first_q400_tail_strike_at_work/, https://www.flightradar24.com/data/aircraft/c-glqp#35e5e56a

Primary Cause

Incorrect approach speed and control adjustments during the touchdown phase, coupled with a lack of sufficient airspeed buffer, resulted in the tailstrike.Incorrect approach speed and control adjustments during the touchdown phase, coupled with a lack of sufficient airspeed buffer, resulted in the tailstrike.

Share on:

Leave a Reply

Your email address will not be published. Required fields are marked *