Incident Bombardier CRJ-900LR N954LR, Wednesday 22 February 2023
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:Wednesday 22 February 2023
Time:18:55
Type:Silhouette image of generic CRJ9 model; specific model in this crash may look slightly different    
Bombardier CRJ-900LR
Owner/operator:Mesa Airlines, opf American Eagle
Registration: N954LR
MSN: 15375
Year of manufacture:2015
Fatalities:Fatalities: 0 / Occupants: 45
Other fatalities:0
Aircraft damage: None
Category:Incident
Location:Hollywood Burbank Airport (BUR/KBUR), Burbank, CA -   United States of America
Phase: Approach
Nature:Passenger - Scheduled
Departure airport:Phoenix-Sky Harbor International Airport, AZ (PHX/KPHX)
Destination airport:Hollywood Burbank Airport, CA (BUR/KBUR)
Investigating agency: NTSB
Confidence Rating: Information verified through data from accident investigation authorities
Narrative:
On February 22, 2023, about 1855 Pacific standard time (PST), Mesa Airlines (dba American Eagle) flight 5826, N954LR, a Bombardier CRJ900 and SkyWest Airlines (dba United Express) flight 5326, N619UX, an Embraer ERJ 170-200, were involved in a loss of minimum separation event at the Bob Hope Airport (BUR), Burbank, CA. The closest proximity was 0.29 miles at the same altitude. There were no injuries reported to the 73 passengers and crew onboard the SkyWest airplane or to the 41 passengers and crew members onboard the Mesa airplane.Mesa Airlines flight 5826 was operating under the provisions of 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from Phoenix Sky Harbor International Airport (PHX), Phoenix, Arizona to BUR. SkyWest Airlines flight 5326 was operating under the provisions of 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from BUR to San Francisco International Airport (SFO), San Francisco, California.

Mesa Airlines flight 5826
The flight crew of flight 5826 reported that they were cleared for the visual approach to runway 33 and instructed to contact the BUR airport traffic control tower (ATCT). After checking in with ATCT they were instructed to “continue for runway 33, traffic holding in position”. After multiple queries to ATCT to obtain a landing clearance with no response, and while on about a 2-mile final approach they were cleared to land followed immediately by a takeoff clearance for flight 5326. Concerned about maintaining adequate separation the flight crew asked ATCT to confirm their landing clearance to which the controller replied affirmative. At about 600 feet above ground level (AGL) and with flight 5326 in sight and beginning their takeoff roll flight 5826 flight crew elected to conduct a go-around. They notified ATCT of the missed approach and were instructed “roger, climb to 4,000 and turn right heading 270. No, left, left turn heading 270”. While in the turn they observed flight 5326 climbing underneath their aircraft and received a traffic advisory (TA) from the onboard traffic and collision advisory system (TCAS). Shortly thereafter, the ATCT instructed them to “turn right heading 240. Wait, left, left turn heading 240”. Having received a resolution advisory (RA) from the TCAS they notified the tower that they were complying with the RA to which she replied “Roger, contact LA approach”. The flight was vectored for another visual approach to runway 33 and landed without further incident.

SkyWest Airlines flight 5326
The flight crew of the flight 5326 reported that they were instructed by air traffic control to back taxi on runway 33 and line up and wait. After what appeared to be a couple minute delay they were cleared for takeoff and subsequently heard the ATCT confirm a landing clearance for another aircraft. Following departure, they turned left to a heading of 270° as required per the departure procedure. While rolling out of the turn they received a TCAS RA alert “descend, descend”. They responded to the RA and resumed normal operations following the TCAS “Clear of conflict” notification.

Burbank Air Traffic Control
The local controller stated that she was distracted by a SR-22 which was instructed to conduct a go-around on runway 26. However, she believed that flight 5326 had been cleared for takeoff when flight 5826 was on about a 2-mile final, and that standard runway separation would have existed had flight 5826 continued to a full stop landing rather than initiating a missed approach. She said the pilot initiated missed approach was unexpected and another controller helped her deconflict the traffic by telling her to “turn them”.

According to FAA Order 7110.65Z, the controller was required to apply a 2-mile separation between a departing aircraft on its takeoff roll and an arriving aircraft on final approach. Radar data indicated that flight 5826 was about 1.5 miles from the runway threshold when flight 5326 was cleared for takeoff and about .80 mile from the runway threshold when they initiated the missed approach.

Investigation
The NTSB formed an Air Traffic Control (ATC) group and the Federal Aviation Administration (FAA), National Air Traffic Controllers Association (NATCA), Mesa Airlines, and SkyWest Airlines are parties to the investigation.

During the week of March 13th, 2023, the ATC group convened at BUR airport traffic control tower (ATCT) and conducted interviews with the Controller in Charge (CIC), Clearance Delivery (CD) controller, the Ground Controller (GC), Operations Supervisor (OS), ATM, and the Local Controller (LC).

Certified ADS-Bdata and audio recordings were provided to the NTSB by the Federal Aviation Administration (FAA).
The NTSB’s Vehicle Recorder Laboratory located in Washington, DC, downloaded data from the digital flight data recorders (DFDRs) from both airplanes. The cockpit voice recorders (CVRs) were overwritten.

The investigation continues.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: 
Status: Preliminary report
Duration:
Download report: Preliminary report

Sources:

https://www.nbcnews.com/news/us-news/mesa-airlines-flight-was-forced-halt-landing-avoid-collision-departing-rcna72141?cid=sm_npd_nn_tw_ma

NTSB
https://www.flightradar24.com/data/flights/aa5826#2f4b8a3a
https://archive.liveatc.net/kbur/KBUR3-Gnd-Twr-App-Feb-23-2023-0230Z.mp3

Location

Revision history:

Date/timeContributorUpdates
18-Jun-2024 22:57 Captain Adam Updated [Time, Total occupants, Location, Source, Narrative, Category, Accident report]

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