N949FD

HISTORY OF FLIGHTThe incident flight crew began the day’s pairing in Ontario, California with a report time of 1850 Pacific daylight time (2050 Central daylight time (CDT)). Their first flight of the evening was from Ontario International Airport, Ontario, California to Fort Worth Alliance Airport (AFW), Fort Worth, Texas. The flight arrived at AFW about 0030 CDT. After postflight procedures each crewmember procured a crew rest room. According to the first officer, he was able to get about 30 minutes of rest prior to preparing for the next flight, which was the incident flight. The captain reported that he attempted to obtain rest, however, he “couldn’t get to sleep.” However, the captain added that he would not have flown fatigued, and he did not feel tired on the incident flight.

The crew reconvened in the preflight briefing room, where they reviewed notices to air mission (NOTAMs) and the weather. Then, they proceeded to the airplane where they conducted preflight checks. About 0330, the flight pushed back from the parking position, taxied out to the runway, and departed AFW for the less than one-hour flight to TUL. The captain was the pilot flying and the first officer was the pilot monitoring. The flight climbed to an enroute altitude of flight level 310 at 0349 and began their descent 2 minutes later.

The first officer stated that at the start of the descent, he obtained the current TUL weather and performance data for the landing. He then proceeded to set up the frequencies for the ILS. Additionally, they created a waypoint about 30 miles from the airport as they wanted to be at 11,000 feet (ft) at that waypoint. The captain briefed the anticipated visual approach, backed up by the ILS, and landing to runway 18L, which included the frequency for the ILS, the Vref speed of 123 knots, and the approach lights for runway 18L.

He also briefed that they would not use the autobrakes, as he wanted to “roll long” as the parking location was at the south end of runway 18L. The flight was transferred from the Federal Aviation Administration (FAA) Air Route Traffic Control Center to the FAA TUL approach controller about 10,000 ft and were issued a heading of 360°, which routed the flight west of the airport. According to the flight crew, the flight was in instrument meteorological conditions at the time.

The flight was given a further descent and then exited the base of the clouds. The first officer reported that when the flight exited the clouds, he could not see the runway but did visually acquire the TUL airport beacon and said it “looked like a normal downwind.” The captain reported that after exiting the clouds he could see the lights for runway 8/26 and that they were “normal.”

The flight crew extended the centerline for runway 18L in their flight management system, which displayed the extended centerline on their ND in the cockpit. Additionally, the first officer verified that the frequency for the ILS 18L was correct and, when the captain requested, extended the flaps to one. The approach controller asked, and the crew verified that they had the airport in sight.

The flight was cleared for the visual approach to runway 18L and cleared to land runway 18L. The captain commanded the autopilot to start the turn to the right and the first officer set 2,400 ft into the altitude preselector, the altitude for the final approach fix as published on the ILS 18L approach chart. During the turn to final about 0410, the captain stated they disengaged the autopilot, extended the flaps to 5, and subsequently configured the airplane for landing which included extending flaps to 30, lowering the landing gear, and conducting the before landing checklist.

According to the FO, while on final approach, the aircraft appeared low visually and he brought that to the captain’s attention. He further explained that the glideslope appeared to be “normal” however, the PAPI lights indicated they were below the runway’s glidepath. Additionally, he stated that the deviation bar on his HSI was deflected to the left; however, during the incident flight he did not bring that to the captain’s awareness.

The captain adjusted the descent rate of the airplane to place the airplane on the visual glideslope as indicated by the PAPI. About a 2.8 mile final and about 800 feet above ground level, the RAAS callout “Approaching 18R” was recorded on the CVR, however this occurred simultaneously with communications in the cockpit and neither crew member acknowledged or recalled this call out.

The captain stated that initially the HUD was showing “slightly off to the left.” However, he transitioned visually to what the PAPI lights were indicating for his vertical alignment with the runway and was more focused on that. The flight touched down about 0413 on runway 18R and the RAAS subsequently announced there was 3,000 ft of runway remaining.

The captain stated during a post incident interview, that he applied the brakes and “came on them harder initially because he was confused.” After slowing the airplane, the captain asked the FO “are we on the correct runway?” and then stated, “we landed on the right [hand] runway.” After informing the controller that they had landed on runway 18R, the controller provided taxi instructions to the ramp. PERSONNEL INFORMATIONThe incident flight crew consisted of a captain and first officer. Both crewmembers stated that this pairing was the first time they had flown with each other.

Captain:

The captain was 57-years-old and held an Airline Transport Pilot (ATP) certificate with a rating for airplane single-engine land and multiengine-land, and type ratings on the A310, B-707, B-720, B-757, B-767 which included limitations of B-757, B-767, A-310 Circling approach – visual meteorological conditions (VMC) Only, and English Proficient. He held an FAA first-class medical certificate dated January 27, 2022, with limitation of must wear corrective lenses. At the time of the incident, he was based at Memphis International Airport (MEM), Memphis, Tennessee.

The captain held over 10,000 hours of total flight experience, 790 of which were as a captain in the B757. During the interview with the captain, he stated that he had flown into TUL “at least a hundred times” and the most recent was about two weeks prior to the incident.

The captain’s account of his sleep in the 72 hours preceding the incident starts the evening of June 5, therefore it is unknown at what time he awoke that morning. He obtained approximately seven hours of sleep, followed by a six-hour period of wakefulness, a two-hour nap, another six-hour period of wakefulness, and a final four-and-a-half-hour period of rest prior to the 0225 crew show on June 7. Following that flight, he slept for approximately five hours. The captain did not have another period of rest before the incident flight. He was awake for approximately 15 hours and 30 minutes prior to the incident occurring.

First Officer:

The FO was 50-years-old and held an ATP certificate with a rating for multi-engine land, single-engine land, rotorcraft-helicopter, instrument helicopter, instrument powered-lift, powered-lift, and type ratings in the A-320, B-757, B-767, with limitations of English Proficient and A-320, B-757, B-767 Circling approach – visual meteorological conditions (VMC) Only . He held an FAA first-class medical certificate dated May 24, 2022, with no medical restrictions. At the time of the incident, he was based at MEM.

The FO held about 4,500 hours of total flight time, 739 of which was as a first officer in the B757. The first officer stated during his interview that it was his second time operating into TUL since his employment began with FedEx 2 years earlier.

The FO’s account of his sleep in the 72 hours preceding the incident starts the evening of June 5, therefore it is unknown at what time he awoke that morning. The longest period of rest was the evening of June 5 to the morning of June 6 where the FO recorded approximately nine hours of sleep. This was followed by a period of wakefulness for approximately 12 hours. A four-hour nap followed and was prior to the 0225 crew show time on June 7. After that flight, the FO recorded another seven hours of sleep, interrupted by a lunch break. The next crew show time was approximately three hours later. Following that flight, the FO took a short, ½ hour nap before the last crew show at 0226 for the incident flight. He was awake for approximately 12 hours since his last prolonged period of rest, and three hours since his nap, prior to the incident occurring. ADDITIONAL INFORMATIONAir Traffic Control Information:

There were two controllers on duty at the time of the incident with one in the tower and one on break. All radar and tower positions were combined to the ground control/ clearance delivery position in the tower. This staffing was the normal mid-shift “TRACAB” configuration, with the controller in-charge position also combined and providing oversight at the time of the incident.

During her interview, the tower controller said she categorized the traffic complexity and volume as being 1 on a scale of 1-5 (5 being high). In a recount of the events, she stated the incident flight had come in from the south, she confirmed they had the current ATIS, and were assigned runway 18L. She then assigned FedEx 1170 a northbound heading and at 6,000 feet, amended their altitude and pointed out the field 10 miles south of their position. The crew reported the field in sight, and she cleared them to land. She then diverted her attention from FedEx 1170 to provide taxi instructions to an unrelated aircraft being repositioned for maintenance.

The tower controller said she conducted a visual sweep of the runway when she initially cleared FedEx 1170 for the approach and to land but admitted she did not look back at the aircraft again. The last time she observed the aircraft on the radar was when it was on a “dogleg” turn to base. FedEx 1170 la...