ASN Wikibase Occurrence # 307465
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: | Saturday 4 February 2023 |
| Time: | 06:40 |
| Type: |  Boeing 737-79P (WL) |
| Owner/operator: | Southwest Airlines |
| Registration: | N7827A |
| MSN: | 28255/1284 |
| Year of manufacture: | 2003 |
| Fatalities: | Fatalities: 0 / Occupants: |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | Austin-Bergstrom International Airport, TX (AUS/KAUS) -
 United States of America
|
| Phase: | Take off |
| Nature: | Passenger - Scheduled |
| Departure airport: | Austin-Bergstrom International Airport, TX (AUS/KAUS) |
| Cancún Airport (CUN/MMUN) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Information verified through data from accident investigation authorities |
On February 4, 2023, at about 0640 central standard time (CST), Federal Express (FedEx) flight 1432 (FDX1432), a Boeing 767-32LF, and Southwest Airlines flight 708 (SWA708) a Boeing 737-79P were involved in a runway incursion with overflight that resulted in a loss of separation at the Austin-Bergstrom International Airport (AUS), Austin, Texas. There were no injuries reported to the 128 passengers and crew onboard the SWA airplane or to the 3 crew members onboard the FedEx airplane. SWA flight 708 was a regularly scheduled international passenger flight operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 from AUS to the Cancún International Airport (CUN), Cancún, Mexico. FedEx flight 1432 was a domestic cargo flight operating under the provisions of 14 CFR Part 121 from Memphis International Airport (MEM), Memphis, Tennessee to AUS.
The Austin Airport Air Traffic Control Tower (AUS ATCT) Air Traffic Manager (ATM) stated at the time of the incident, there was an extremely low traffic volume and complexity at AUS. The weather at the time of the incident was low instrument flight rules with the following conditions being reported: wind calm, visibility 1/4 mile in freezing fog, vertical visibility 200 ft above ground level, and a temperature minus 1 degree Celsius.
A review of Federal Aviation Administration air traffic control (ATC) audio recordings indicated that at about 0634, the pilots of FDX1432 established communication with the local controller and reported their flight was inbound and established on a CAT III instrument landing system (ILS) approach to runway 18L. The controller provided the pilots with the runway visual range (RVR) values and cleared them to land. The pilots acknowledged this information.
At 0638:49, the first officer (FO) of SWA708 checked in with the local controller and indicated they were holding short of runway 18L and were ready for takeoff. The controller provided them with RVR values, advised them that a FedEx 767 was on a three-mile final (FDX1432), and issued them a standard takeoff clearance from runway 18L. The FO of SWA708 acknowledged the clearance with a correct readback. SWA708 proceeded to taxi onto runway 18L and lined up with the runway centerline and came to a complete stop at which point, control of the aircraft was transferred from the captain to the FO. The FO indicated that he advanced the power, checked the engines, and then released the brakes to begin their takeoff roll.
At 0639:32, the pilots of FDX1432 queried the local controller to confirm that they were cleared to land on runway 18L. According to the captain of FDX1432, he asked for confirmation because he was concerned about the Southwest traffic. The controller confirmed FDX1432 was cleared to land and advised them of traffic (SWA708) departing runway 18L ahead of him.
At 0640:12, with FDX1432 on an approximate 0.7-mile final, the local controller queried SWA708 to confirm they were on the roll, to which the captain of SWA708 replied “rolling now.” According to the captain of FDX1432, he noted that at an altitude of about 150 feet, the FO called go-around after visually seeing SWA708 at approximately 1,000 feet to 1,500 feet from the approach end of the runway. At 0640:34 one of the FDX1432 crew broadcasted “Southwest abort” and then at 0640:37 broadcasted that “FedEx is on the go.” According to the SWA708 pilot narratives, the captain noted that somewhere between the speeds of 80 KIAS and V1, he and the first officer heard FedEx call for a go-around.
A review of preliminary Automatic Dependent Surveillance-Broadcast (ADS-B) data revealed that when FDX1432 was at the departure end of the runway climbing out of 1,900 feet, the controller instructed FDX1432 to turn left heading 080 and maintain 3,000 feet. At the same time, SWA708 was about 1,000 ft lower than FDX1432 and began a right turn away from the runway heading.
The AUS ATCT ATM reported an overflight appeared to have occurred; however, the closest proximity has not yet been determined. SWA708 continued their flight plan route to Cancún, and FDX1432 executed a go-around and returned for landing without incident on runway 18L.
Upon notification, the following NTSB investigative groups were formed for this investigation: operations, human performance, air traffic control, meteorology, and flight data recorder. Parties to the investigation include the Federal Aviation Administration (FAA), Federal Express, Southwest Airlines, National Air Traffic Controllers Association (NATCA), Air Line Pilots Association, International (ALPA), Southwest Airlines Pilots Association (SWAPA), Boeing and Honeywell Aerospace.
Certified ADS-B data and audio recordings were provided to the NTSB by the Federal Aviation Administration (FAA). The NTSB is currently analyzing this data.
The digital flight data recorders (DFDRs) were removed from both airplanes and shipped to the NTSB’s Vehicle Recorder Laboratory located in Washington, DC. Both DFDRs have been downloaded, and the data is currently being analyzed. The cockpit voice recorders (CVRs) were overwritten.
During the week of February 6th, 2023, the ATC group convened at AUS ATCT, the facility that was providing services to both airplanes at the time of the incident and conducted interviews with the Local Controller and Operations Supervisor that were working at the time of the incident, as well as the NATCA Facility Representative and Air Traffic Manager. In addition to the ATC personnel, the group also interviewed the Contract Weather Office Supervisor.
During the week of February 13th, 2023, the Operations group conducted interviews with the pilots of FDX1432 and with the pilots of SWA708.
The traffic alert and collision avoidance system (TCAS) computers have been removed from both airplanes and have been sent to their respective manufacturers for a download of data. On February 16th, information from the Southwest TCAS unit was downloaded and is currently being analyzed.
Sources:
https://abcnews.go.com/US/wireStory/crash-averted-austin-airport-faa-ntsb-investigate-968993953
NTSB
https://flightaware.com/live/flight/N7827A/history/20230204/1235Z/KAUS/MMUN
https://globe.adsbexchange.com/?icao=aa9b42&lat=30.194&lon=-97.655&zoom=16.0&showTrace=2023-02-04&leg=3×tamp=1675514438
https://www.flightradar24.com/blog/ntsb-faa-investigating-fedex-southwest-close-call-in-austin/
https://www.planespotters.net/photo/1279944/n7827a-southwest-airlines-boeing-737-79pwl (photo)
Media:
ATC Recording of the Austin Airport incident! 😳
— John-Carlos Estrada (@Mr_JCE) February 5, 2023
Close call at AUS this morning after a FedEx 767 was cleared to land while a Southwest 737 was still on the runway. pic.twitter.com/gAss8daltn
Revision history:
| Date/time | Contributor | Updates |
|---|
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation