Runway incursion Accident Raytheon Hawker 850XP N269AA,
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 24 October 2023
Time:15:20
Type:Silhouette image of generic H25B model; specific model in this crash may look slightly different    
Raytheon Hawker 850XP
Owner/operator:Whitmore Holdings LLC
Registration: N269AA
MSN: 258800
Year of manufacture:2006
Engine model:Honeywell TFE731-5BR-1H
Fatalities:Fatalities: 0 / Occupants: 3
Aircraft damage: Substantial
Category:Accident
Location:William P. Hobby Airport (HOU/KHOU), Houston, TX -   United States of America
Phase: Take off
Nature:Private
Departure airport:Houston-William P. Hobby Airport, TX (HOU/KHOU)
Destination airport:Waukesha Airport, WI (UES/KUES)
Investigating agency: NTSB
Confidence Rating: Information verified through data from accident investigation authorities
Narrative:
On October 24, 2023, about 15:20 central daylight time, a Raytheon Hawker 850XP, N269AA, was taking off on runway 22 when its left wing collided with the vertical stabilizer of a Textron Aviation (Cessna) Citation Mustang, N510HM, that was landing on runway 13R at William P. Hobby Airport (HOU), Houston, Texas. Day visual meteorological conditions prevailed at the time of the accident.

There were no injuries to the 2 pilots and 1 passenger aboard N269AA or to the 1 pilot and 3 passengers aboard N510HM. N269AA sustained minor damage and N510HM was substantially damaged during the collision. N269AA was operating as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand passenger flight from HOU to Waukesha County Airport (UES), Waukesha, Wisconsin. N510HM was operating as a Title 14 CFR Part 91 flight from Fulton County Executive Airport/Charlie Brown Field (FTY), Atlanta, Georgia, to HOU.

HOU has intersecting runways, and the local controller had instructed the crew of N269AA to line up and wait (LUAW) on runway 22. The crew of N269AA said in a post-accident interview that they believed they heard that they were cleared for takeoff when they took off. The collision between the two airplanes occurred at the intersection of the two runways,.

According to FAA record of communications, at 1514:12 the crew of N269AA had contacted ground control (GC) requesting clearance to taxi for departure.

About a minute later, the pilot of N510HM checked in with local control (LC) while on a ninemile final to runway 13R. The local controller then cleared the pilot of N510HM to land. The pilot of N510HM read back the landing clearance.

As N269AA approached runway 22 for departure, about 1515:50, ground control instructed the crew of N269AA to monitor LC frequency. The flight crew stated in their post-accident interview that as they passed taxiway “K2” during their taxi to runway 22 they switched to the LC frequency. As the airplane began the left turn to be perpendicular to the runway, they stated the V-speeds were no longer on the display screens.

At 1517:32 the pilot of N510HM reported a four-mile final.

At 1518:01 the local controller instructed the crew of N269AA to LUAW on runway 22, to which the crew acknowledged. The local controller did not give a traffic advisory to N269AA.

N269AA was in the takeoff roll on runway 22, when the flight data/clearance delivery controller alerted the local controller about N269AA’s movement, and at 1519:47 the local controller stated “november nine alpha alpha, stop, hold your position.” There was no response from the crew of N269AA, and at 1519:53 the local controller again stated, “alpha, alpha, hold your position, stop,” to which there was still no response.

The flight crew from N269AA stated in their post-accident interview they had a rudder bias alert, and a pitch trim alert which they had to resolve as they were in the takeoff roll.

Both crew members in N269AA said that they did not see the Citation Mustang until about 1 second prior to impact and described the feeling of the impact as a “thud.” The pilot in the left seat was the pilot flying (PF) and the pilot in the right seat was the pilot monitoring (PM).

At 1520:00, N269AA collided with N510HM. At 1520:14, the local controller began providing instructions to send around all aircraft that were on final approach behind N510HM.

At 1520:29 the crew of N269AA, who had taken off and was in the initial climb, informed local control that they needed to return to the airport, and the local controller provided vectors to return to the airport and land on runway 13R.

At 1521:08 The local controller cleared N269AA to land on runway 13R, and the flight landed otherwise uneventfully.

In the post-accident interview N510HM pilot said that he did not see N269AA airplane but heard a sound similar to a truck tire blowing out on a highway. N269AA crew stated that their airplane did not yaw, and they experienced no controllability issues during the takeoff. They were only aware of damage after parking and exiting the airplane

Airport Surface Detection Equipment:

HOU tower is equipped with an Airport Surface Detection Equipment – Model X (ASDE-X) system, with displays located at the LC, GC, operations supervisor, and helicopter position workstations.

ASDE-X is a surface movement radar that enables air traffic controllers to detect potential runway conflicts by providing detailed coverage of movement on runways and taxiways. ASDEX collects data from a variety of sources to track vehicles and aircraft on the airport movement area and obtain identification information from aircraft transponders.

The controllers noticed N269AA’s movement before the ASDE-X alert which occurred at 1519:49.

Aircraft Damage Assessment:

Post-accident examination of N269AA revealed that the left wing exhibited impact damage. The titanium leading-edge panel exhibited a “V-shape” aft indention to the wing front spar with sheet metal remnants of the Cessna Mustang embedded.

N269AA’s left-wing winglet remained attached to the left wing. The winglet leading edge exhibited white paint transfer marks and the navigation light lens was impact separated and pieces of the glass were found in the Cessna Mustang’s tail cone/stinger. About ten inches of the top section of N269AA’s winglet had separated due to the impact with N510HM.

Post-crash examination of N510HM revealed that the left side of its tail section had been impacted by the left wing of N269AA. The torn skin on the tail section was consistent with N269AA’s wing penetrating the left side of N510HM’s tail stinger and exiting the right side, severing a portion of the stinger. The impact damage was isolated to the area of the empennage.

The impact fractured and separated a section of the aft canted bulkhead. A section of the aft horizontal stabilizer spar; common to the rudder sector attach point, was torn and bent consistent with the wing impact. The rudder sector mount was torn from the structure at the fastener locations.

The rudder torque tube was fracture separated from the rudder control sector and the rudder. The upper and lower left and lower right rudder control cables were broken in a manner consistent with tensile overload. The upper right rudder control cable remained intact, but the ball end was pulled from the rudder sector. The autopilot rudder servo control cable was fractured in tensile overload. The left autopilot cable pulley bracket, with pully attached, was separated from the canted bulkhead. The left strake was impact fractured from the tail cone stinger and was recovered from the runway along with various sheet metal fragments from the stinger

The following NTSB specialists have been assigned to investigate the accident: operations, human performance, air traffic control, and cockpit voice recorder (CVR). The Federal Aviation Administration (FAA), National Air Traffic Controllers Union (NATCA), Textron Aviation, DuPage Aerospace Corporation (operator of N269AA), and My Jet DOM, LLC (operator of N510HM), are parties to the investigation.

N269AA was equipped with a CVR, which was removed and sent to the NTSB Vehicle Recorder Laboratory in Washington, DC, for download and analysis. N510HM was not equipped with recorders.

The investigation is continuing.

Sources:

https://abc13.com/why-is-hobby-airport-flights-grounded-houston-runway-incident-skyeye-13-private-plane-winglet-clipped/13965780/

NTSB
https://www.flightaware.com/live/flight/N269AA/history/20231024/2015Z/KHOU/KHOU

Location

Media:

Revision history:

Date/timeContributorUpdates
25-Oct-2023 05:45 Captain Adam Added
25-Oct-2023 07:40 harro Updated
08-Nov-2023 22:30 Captain Adam Updated [Time, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org