PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Accidents and Close Calls (https://www.pprune.org/accidents-close-calls-139/)
-   -   NTSB to probe Fedex/Southwest close encounter at Austin (https://www.pprune.org/accidents-close-calls/651189-ntsb-probe-fedex-southwest-close-encounter-austin.html)

voyageur9 5th Feb 2023 00:06

NTSB to probe Fedex/Southwest close encounter at Austin
 
Landing Fedex and Southwest taking off at Austin

DIBO 5th Feb 2023 01:02

Too close for comfort...

Note: the left turn by Fedex plane as depicted by the FR24 'playback' in bottom right corner of picture below, is overly exaggerated (it was still more or less in the centerline at the end of the rwy)
https://cimg0.ibsrv.net/gimg/pprune....d9281bac79.jpg

Vertical separation was already substantial by the end of the runway, but the flightpath of SWA708 (especially the RoC) moments after liftoff was kind of aah... interesting: https://www.flightradar24.com/data/f...wn708#2f136f25


JohnnyRocket 5th Feb 2023 01:32

Landing FedEx cargo plane almost crashes into Southwest Airlines plane taxiing on run
 
Looks like a landing FedEx cargo plane almost crashed into Southwest Airlines plane taxiing on runway at Austin International Airport

https://twitter.com/IntelPointAlert/status/1622057477310144513

https://flightaware.com/live/flight/FDX1432

megan 5th Feb 2023 02:04

One comment says dense fog, whereas the link says "The incident occurred in poor visibility conditions".

https://www.reuters.com/world/us/us-...as-2023-02-04/

megan 5th Feb 2023 02:10

Weather reported as dense fog or poor visibility depending on source.

ATC Watcher 5th Feb 2023 08:47

The traditional go around above a take off , the absolute nightmare of every Tower controller as you can only sit and watch. , nothing much you can do exept take a few degrees off centre line.when going around and then only if there is no parallel runway in there... Fog or no fog, makes no difference as both aircrfat cannot see ( and avoid) each other.in this configuration .

DaveReidUK 5th Feb 2023 10:29

FR24 data is disappointingly sparse - in particular there's a 27-second gap around the point where the SWA started to roll (not helped by FR24's built-in asynchronicity between position and velocity data).

The altitude plot for the FedEx (after adjusting for QNH and runway elevation) suggests that it came within a gnat's of the runway surface and may even have touched down during the GA. At that point (again subject to the above asynchronicity uncertainty) FR24 suggests the SWA was rolling at 85-90 kts and longitudinal separation was around 500'.

Usual FR24 caveats apply, probably even more so in this instance ...

340drvr 5th Feb 2023 10:38

Definitely low vis conditions:
Code:

KAUS 041247Z 00000KT 1/8SM R36R/1800V2400FT FZFG VV002 M01/M01 A3043 RMK AO2
Code:

KAUS 041218Z 00000KT 1/4SM R36R/1800V2400FT FZFG VV002 M01/M01 A3043 RMK AO2 T10061006

voyageur9 5th Feb 2023 12:05

From FR24

https://twitter.com/i/status/1622067973111308288


wd-15717 5th Feb 2023 12:35

Fully realize SOP in the US is clear to land even when the runway is occupied, but how on earth do you give that clearance in zero visibility conditions?

Between this and JFK near miss, I think it’s time for the FAA to revisit some atc protocols.

(I believe JFK was entirely fault of AA pilots, but “NY style” atc didn’t help matters)

ATC Watcher 5th Feb 2023 14:43


Originally Posted by wd-15717 (Post 11380385)
Between this and JFK near miss, I think it’s time for the FAA to revisit some atc protocols.
(I believe JFK was entirely fault of AA pilots, but “NY style” atc didn’t help matters)

And what makes you think it is ATC at fault here ? Looking at the FR24 construction it looks like one is slowly lining up and take off ,( with or without clearance) with another on finals . Nothing much else . For all we know it could be Southwest who has to "revesit" something .

Most of the incidents like this I saw in my carreer were when a "ready for immediate departure?" request is being mishandled by the crew . If ATC played it too tight here , time will tell, but I wait to read or hear a time stamped tape before passing any judgement .
As to the go around procedure, with a take off below ,yes it is a well known loophole with no real solution . Most of the times it it solved as the go around goes above the departure ( like here) but there is no gauarantee, I saw once an A340 on a late go around continue descending and touch down the runway before going up again.

Una Due Tfc 5th Feb 2023 14:59

Clearing the 737 onto the runway with the 767 at 3nm in LVPs is cutting it very very tight....

BFSGrad 5th Feb 2023 15:11


Originally Posted by ATC Watcher (Post 11380424)
And what makes you think it is ATC at fault here ?

After Fedex clears the runway after landing, tower says “you have our apologies, we appreciate your professionalism.”

jetpig32 5th Feb 2023 16:01

Interesting. I was departing 30 mins later. After much confusion from ground control on taxi out as to where everyone was, we had a 40 min hold for release time. We sat short 18L monitoring tower and shooting the breeze. Let me set it all up.
1) 18r is preferred departures in AUS in the am. No CL lights, so 1000rvr. All aircraft (well most) were requesting 18L, and ground seemed agitated.
2) There is no ground surveillance, so ground was often forgetting where each plane was. (Shocked in adsb age, there’s no low cost solution the could budget for.
3) due single runway and no ground radar, line-up-wait not utilized.
4) tower, at this time, seemed to be giving extra large spacing between departing and landing traffic. Like 10 miles. (Now I know why)

I commented on this to my FO, and said this could get messy if they tighten up arrivals/departures and someone rejected or misunderstood the immediate to clearance. I’m single rw ops, our expectation bias is line up and wait. Don’t know what took the Southwest so long as they always seem in a rush. Perhaps when he called ready, they weren’t quite, or even near the hold bars yet. Seems common for them to call ready 100m away from holding point. Tower would have no idea that they weren’t quite there yet.

MLHeliwrench 5th Feb 2023 16:23


Originally Posted by jetpig32 (Post 11380452)
Interesting. I was departing 30 mins later. After much confusion from ground control on taxi out as to where everyone was, we had a 40 min hold for release time. We sat short 18L monitoring tower and shooting the breeze. Let me set it all up.
1) 18r is preferred departures in AUS in the am. No CL lights, so 1000rvr. All aircraft (well most) were requesting 18L, and ground seemed agitated.
2) There is no ground surveillance, so ground was often forgetting where each plane was. (Shocked in adsb age, there’s no low cost solution the could budget for.
3) due single runway and no ground radar, line-up-wait not utilized.
4) tower, at this time, seemed to be giving extra large spacing between departing and landing traffic. Like 10 miles. (Now I know why)

I commented on this to my FO, and said this could get messy if they tighten up arrivals/departures and someone rejected or misunderstood the immediate to clearance. I’m single rw ops, our expectation bias is line up and wait. Don’t know what took the Southwest so long as they always seem in a rush. Perhaps when he called ready, they weren’t quite, or even near the hold bars yet. Seems common for them to call ready 100m away from holding point. Tower would have no idea that they weren’t quite there yet.

I also wonder if the call of ‘rolling’ by SWA was a bit optimistic. Perhaps they were still turning on to active or otherwise not quite rolling yet.

fluglehrer 5th Feb 2023 16:43

is there an audio? glad no crash!

Vlad the Impaler 5th Feb 2023 16:49

Listening to the RT the tower controller seems strangely absent in the process. RVR given with T/O clearance was foggy but not yet CAT II/III ops. Nonetheless, especially without the benefit of ground radar that sounded super tight. What concerns me the most is that it's not the Tower controller who calls abort. Its the FedEx crew just before they call going around. I don't want to hang the atc out to dry but on the RT replay alone that is total dereliction of duty for me. I speak as a 20yr tower ATCO well used to low visibility ops.

mike current 5th Feb 2023 16:52


Originally Posted by ATC Watcher (Post 11380424)
And what makes you think it is ATC at fault here ? Looking at the FR24 construction it looks like one is slowly lining up and take off ,( with or without clearance) with another on finals . Nothing much else . For all we know it could be Southwest who has to "revesit" something .

Most of the incidents like this I saw in my carreer were when a "ready for immediate departure?" request is being mishandled by the crew . If ATC played it too tight here , time will tell, but I wait to read or hear a time stamped tape before passing any judgement .

You don't play it tight in Low Vis conditions. There are parameters to meet to ensure Cat 3 protection.
Take off roll must commence by inbound at X miles.. landing clearance received no later than X miles etc.
These are UK rules but I'm sure the FAA must have similar otherwise how do you safeguard Cat 3 operations?

(I don't know whether this incident was in Cat 3 conditions, but the safeguarding in Low Vis must offer protection of some sort).

Zeffy 5th Feb 2023 18:22


Originally Posted by mike current (Post 11380475)
(I don't know whether this incident was in Cat 3 conditions, but the safeguarding in Low Vis must offer protection of some sort).

At the beginning of the recording, FedEx checks in as a Cat III arrival.
https://forums.liveatc.net/atcaviati...sion/msg75658/

DaveReidUK 5th Feb 2023 18:50


Originally Posted by MLHeliwrench (Post 11380460)
I also wonder if the call of ‘rolling’ by SWA was a bit optimistic. Perhaps they were still turning on to active or otherwise not quite rolling yet.

FR24 have now released (slightly) more granular data which provides more detail around the SWA's runway entry and line up.

The 737 appears to have been stationary for approximately 20 seconds between lining up and starting to roll (stated purely as a matter of record, no judgement implied).


All times are GMT. The time now is 01:36.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.