N412JARaytheon Aircraft HAWKER 800XP · 2001

On December 20, 2020, about 2035 eastern standard time, a Raytheon Aircraft Company Hawker 800XP, N412JA, was substantially damaged when it was involved in an accident near Farmingdale, New York. The captain sustained minor injuries and the first officer was seriously injured. The airplane was operated by Talon Air, LLC as a Title 14 Code of Federal Regulations (CFR) Part 91 business flight.

The captain was the pilot monitoring (PM), and the first officer was the pilot flying (PF) at the time of the accident. The captain and first officer stated that the flight was normal. As they approached the destination airport, they were vectored for the instrument landing system (ILS) runway 14 approach. The weather was at minimums (overcast at 200 ft above ground level [agl] and ¾-mile visibility) for the approach. The pilots briefed the approach, and the airplane was fully configured to land upon reaching the final approach fix (FAF). Both pilots said that, after passing the FAF, the tower controller reported that weather conditions had deteriorated to 200 ft agl and ¼-mile visibility. The captain asked the first officer if he wanted to continue with the approach, and he said he did. The first officer said that he was using the autopilot on the approach, the airplane was stabilized, and he felt they could safely descend to minimums.

The airplane was equipped with a cockpit voice recorder (CVR). Review of the recording revealed that, at 2034:56, when the airplane reached the decision altitude of 200 ft agl (as indicated by the recording’s capture of an aural minimums callout from the airplane’s radio altimeter), the captain declared that he had runway environment lights in sight. The first officer responded that he would continue with the approach. At 2035:01, the captain saw the flashing sequence lights for the approach lighting system and the red terminating bars and asked the first officer if he could see them. The first officer responded that he was prepared to land the airplane and continued with the approach. At 2035:08, the captain stated he had the runway in sight. At 2035:11, as the airplane reached 50 ft agl, a sound consistent with the autopilot disconnecting was heard.

Between 2035:16 and 2035:18, as the airplane descended from 30 to 20 ft agl, the captain told the first officer three times to flare the airplane, and noted that the airplane was moving to the right of the runway centerline. Three seconds later, the first officer told the captain to take control of the airplane, while the captain simultaneously called for a go-around. The first officer responded by adding full power and called for the flaps to be retracted to 15º. About 5 seconds later, the airplane impacted the ground.

The first officer stated that, as the airplane approached 200 ft agl, the captain announced “minimums, lights.” He looked outside, saw the “lead-in” lights, and announced, “continuing,” and returned to flying the airplane via instruments. He said that, as the airplane descended to 100 ft agl, the captain told him the runway was to the left. He looked out and saw that the weather was worse than he expected, as if a “black cloud” was sitting at the end of the runway. He said the conditions were not “good enough for him,” and he hit the takeoff/go-around (TOGA) switch while, at the same time, the captain called for a go-around. The first officer said that he added full power and called for flaps 15 degrees, but just as he started to pull up, the airplane landed on the runway “on the hard side.”

The captain stated that, when the airplane was between 50 and 100 ft, it began drifting to the right, and he told the first officer to make a correction. The captain said that the correction was not sufficient to realign the airplane with the runway centerline, and he called for a go-around. The captain said the airplane pitched up in response to the TOGA switch, and he heard both engines spool up as he retracted the flaps, but the airplane did not climb. The airplane then impacted the ground, veered right, and spun before coming to a stop. When asked about first officer’s request to initiate a transfer control of the airplane, the captain said, “I believe the request was made with the intent of salvaging the landing. If memory serves me right, just after the request I ordered the go around. I did not place my hands on the controls.”

The captain held an airline transport pilot certificate and was type-rated in the Hawker 800/900. He reported a total flight experience of 4,188 hours, of which 2,060 hours were in the accident airplane make and model. The captain held a current Federal Aviation Administration (FAA) first-class medical certificate with no restrictions or limitations.

The first officer held an airline transport pilot certificate and was type-rated in the Hawker 800/900. He reported a total flight experience of 10,000 hours, of which 4,100 hours were in the accident airplane make and model. The first officer held a current FAA first-class medical certificate with no restrictions or limitations.

Both pilots stated that they had flown the ILS runway 14 approach numerous times and were familiar with the approach. A review of both the captain’s and first officer’s company training records revealed that they each received and successfully passed training on missed approaches from a precision approach and also rejected landings, which were initiated from 50 ft agl.

Runway 14 was a 6,833-foot-long by 150-foot-wide asphalt runway. It was equipped with a medium intensity approach lighting system with sequence flashers (MALSF). There were no runway centerline lights.

A review of the remarks section of the ILS or LOC runway 14 approach plate revealed that an autopilot-coupled approach was not authorized below 310 ft msl (240 agl). In a postaccident interview, the first officer mentioned that he used the autopilot for the approach but did not recall when he turned it off.

A special weather update at 2033 reported wind from 080° at 3 knots, visibility ¼-mile, fog, vertical visibility 200 ft, temperature 1° C, dewpoint -1° C, with a barometric pressure setting of 30.02 inches-Hg.

According to an FAA inspector who spoke with two first responders to the accident, the fog had “quickly” and “unexpectedly” developed on the airport around the time of the accident.

An FAA inspector who responded to the accident site stated that the airplane impacted the right side of the runway, about 2,000 ft down, then veered right of the runway about 1,500 ft before coming to rest. The nose wheel and both main landing gear departed the airplane and were found on the runway. There was no postimpact fire. The airplane sustained substantial damage to the fuselage.

The airplane was not equipped with a flight data recorder (FDR); however, each engine was equipped with a digital electronic engine control unit. Data downloaded from both units revealed that there was a go-around attempt and both engines responded simultaneously to power lever inputs. Both engines achieved 90-95% N1 speed in about 5 to 6 seconds. No mechanical issues with the airplane or engines were reported by either crew member or the operator.

The Talon Air General Operations Manual (GOM) (section 19.2.- STABILIZED ON PROFILE) stated:

The airplane must be in the proper landing configuration, on the correct track, on the correct lateral track, the correct vertical track and the airspeed within the acceptable range specified in the AFM [airplane flight manual] or POH [pilot’s operating handbook], as applicable. It should be noted, as it applies to stabilized approaches, that following lateral and vertical tracks should require only normal bracketing corrections. An approach that requires abnormal bracketing does not meet the stabilized approach concept, and a go-around should be initiated.

The Standard Operating Procedures section of the GOM (section 2.5. - POSITIVE TRANSFER OF CONTROLS), stated:

If the primary responsibility for controlling the aircraft is transferred from one pilot to the other once airborne, the person designated as the PF will brief the PM with the following basic information prior to initiating positive transfer of controls.

1. Aircraft altitude instructions.

2. Navigation instructions.

3. Pertinent information regarding aircraft configuration or ATC clearance.

To initiate positive transfer of controls the PF will state, “you have the controls”. The pilot receiving aircraft control will then confirm transfer of control by stating, “I have the controls”, which indicates that he/she understands and has control of the aircraft.