PPRuNe Forums - View Single Post - NTSB to probe Fedex/Southwest close encounter at Austin
Old 13th Feb 2023, 00:35
  #209 (permalink)  
BFSGrad
 
Join Date: Mar 2015
Location: Virginia, USA
Posts: 460
Likes: 0
Received 26 Likes on 17 Posts
Listened to comms before/after widely-publicized tower comm segment associated with this incident. Here’s what I learned:

Austin approach/departure positions were combined (same voice) and not busy.

Female voice on ground control. Tower/ground positions were not combined.

ATIS India (WN708 reported receiving, assume FDX1432 received same) stated ‘arrivals expect ILS approach 18 right, 18 left, simultaneous approaches in use.’ No mention of ‘low visibility ops’ other than reported weather.

WN708 taxi instructions were G2, G, B, report turning onto G.

About 1 minute later WN708 reports reaching G. Ground then directs WN708 to contact tower on 121.0 upon reaching 18L. Assumption is that WN708 continues to monitor ground until reaching 18L at B. About 2.5 minutes later (assuming that LiveATC files are time synchronized), WN708 contacts tower and reports ready at 18L.

After go around, FDX contacts approach and requests ‘long vectors for Cat III ILS 18L.’ Sometimes approach will ask reason for go around. Not this time.

After landing and contacting ground, Fedex receives taxi instructions but no further discussion with ground regarding incident (post-local controller apology on tower freq).

About 2 minutes after FDX1432 reports clear of 18L, same local controller withholds a takeoff clearance for an AA reporting ready for departure at 18L with another AA reported on a 2-mile final Cat III ILS for 18L.

No further discussion of incident after WN708 checks in with departure.

Same local controller issues ‘turn right when able’ instruction (twice) to AA after landing on 18L. IMO, this supports theory that, when local controller used identical instruction for WN708, he thought that WN708 had aborted his takeoff.

Regarding comment that “ready” call upon reaching runway is inappropriate, all of the departing aircraft reported “ready,” “ready for departure,” or “in sequence” upon reaching the assigned departure runway.

About 17 minutes after the FDX/WN incident, a new voice appeared on the tower frequency; i.e., local position was changed.
BFSGrad is offline