Go Back  Airline Pilot Central Forums > Pilot Lounge > Safety
Another "near miss" at AUS >

Another "near miss" at AUS

Search
Notices
Safety Accidents, suggestions on improving safety, etc

Another "near miss" at AUS

Thread Tools
 
Search this Thread
 
Old 02-07-2023, 02:18 AM
  #71  
Gets Weekends Off
 
USMCFLYR's Avatar
 
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
Default

Originally Posted by rickair7777 View Post
I don't see any ILS critical markings around 18L. In that case the regular hold-short lines are far enough away IIRC, and they are set pretty far back in the hold bay.

Don't know about whether position and hold on the numbers would violate the critical area, might be far enough away on a long runway but presumably a departure *would* bust it at some point on the takeoff roll.
Big chucks of metal anywhere on the runway can cause interference with the LOC signal - which is of course very important during a CAT III approach.

In addition - as the aircraft taking off down the way, breaks ground and continues to fly over the LOC antennas, there is certainly going to be interference, thus having an aircraft takeoff when another aircraft is using the LOC signal on a CAT III approach is probably not a good idea. I don't know the P121 world's rules on CAT III approaches and what indications on the approach may cause the call for a missed approach, but I do know how tight those CAT III LOC tolerances are and what little interference it takes to bust the structure tolerances in particular.
USMCFLYR is offline  
Old 02-07-2023, 02:30 AM
  #72  
Gets Weekends Off
 
USMCFLYR's Avatar
 
Joined APC: Mar 2008
Position: FAA 'Flight Check'
Posts: 13,837
Default

Originally Posted by Otterbox View Post
Maybe SWA wasn’t on tower when FedEx was cleared to land?
Maybe Engine Warmup/Runup time caused a delay? Or additional taxi time from behind the ILS hold short?
A variety of factors it sounds like for the additional time for a LIFR takeoff that I'm hearing about from other P121 pilots, but in regard to the bolded above - there is no ILS hold short line on the west side of RWY 18L.
USMCFLYR is offline  
Old 02-07-2023, 01:10 PM
  #73  
Me? Just lucky to be here
 
Bo Darville's Avatar
 
Joined APC: Sep 2021
Position: 757/767 FO
Posts: 80
Default

Sounds like everyone is agreed the TWR should not have cleared SWA for takeoff. But I don’t agree with the idea SWA now owns the runway, as mentioned and implied. FDX threw out a big clue to SWA confirming landing clearance at about 2DME.

Now I know we all have the clarity of hindsight but can anyone here honestly say, “yeah, I’d continue taking the runway with another plane at 2DME in low vis” especially if you need to conduct a run and/or standing takeoff? And if your answer is yes, what’s your limit?

Every pilot has an obligation to break the safety chain. In this case, the SWA crew might have already crossed the hold line when they realized something’s not right. Stop, radio tower, and let tower cancel FDX landing clearance.

Any pilot who tells themself, “tower cleared me so I own the runway” is absolutely correct…right up to the point of impact. No one ever owns any piece of pavement or airspace just because ATC says so.

-Bo
Bo Darville is offline  
Old 02-07-2023, 02:43 PM
  #74  
Gets Weekends Off
 
Joined APC: Jun 2016
Posts: 428
Default

Originally Posted by Bo Darville View Post
Sounds like everyone is agreed the TWR should not have cleared SWA for takeoff. But I don’t agree with the idea SWA now owns the runway, as mentioned and implied. FDX threw out a big clue to SWA confirming landing clearance at about 2DME.

Now I know we all have the clarity of hindsight but can anyone here honestly say, “yeah, I’d continue taking the runway with another plane at 2DME in low vis” especially if you need to conduct a run and/or standing takeoff? And if your answer is yes, what’s your limit?

Every pilot has an obligation to break the safety chain. In this case, the SWA crew might have already crossed the hold line when they realized something’s not right. Stop, radio tower, and let tower cancel FDX landing clearance.

Any pilot who tells themself, “tower cleared me so I own the runway” is absolutely correct…right up to the point of impact. No one ever owns any piece of pavement or airspace just because ATC says so.

-Bo
I wasn’t there so no comment on who should have done what but this is a good learning moment for all of us to hone up our SA skills.

Fate is the hunter.
CoefficientX is offline  
Old 02-07-2023, 04:53 PM
  #75  
Gets Weekends Off
 
dmeg13021's Avatar
 
Joined APC: Mar 2014
Posts: 699
Default

How often does AUS deal with <Cat I conditions? Icing? How many times had tower cleared a SWA no problem with plane on final? Run up and ILS protection may not have even occurred to controller when previous 1000 takeoff clearances were day VMC.
dmeg13021 is online now  
Old 02-07-2023, 06:37 PM
  #76  
Disinterested Third Party
 
Joined APC: Jun 2012
Posts: 6,026
Default

Originally Posted by dmeg13021 View Post
How often does AUS deal with <Cat I conditions? Icing? How many times had tower cleared a SWA no problem with plane on final? Run up and ILS protection may not have even occurred to controller when previous 1000 takeoff clearances were day VMC.
One hopes the controller is managing the flight that's happening now, rather than the one that happened takeoffs or landings ago.
JohnBurke is offline  
Old 02-08-2023, 05:05 AM
  #77  
Gets Weekends Off
 
Joined APC: Feb 2022
Posts: 443
Default

Originally Posted by Palmtree Pilot View Post
They didn’t request a T/O clearance.
They reported ready reaching the runway.
You can have your own opinion and it doesn’t have to agree with mine but they didn’t say what you said either, see the problem?
Round Luggage is offline  
Old 02-09-2023, 05:22 AM
  #78  
Gets Weekends Off
 
Vito's Avatar
 
Joined APC: Nov 2005
Position: 757/767 Capt
Posts: 642
Default

Spoiler
 
I’ll throw this out there for discussion. SouthWest’s call to Tower, stating “Southwest Holding short Rwy 18L , we’re ready” was totally unnecessary and One can argue was the catalyst of this entire incident.

Number One, Why make that call? Who cares?. It accomplished nothing except to clog up the Tower freq with unnecessary chatter while another aircraft is attempting to fly a Cat 3 approach.

Number 2, This call prompted the Tower controller to issue a dubious takeoff clearance, which, if the call was never made, the Takeoff clearance would never have been issued.

Number 3, it set up a situation where SW had to rush his takeoff roll, if he were even aware enough to realize how close FedEx was.
And this call possibly caused Tower, out of habit, to clear SW for takeoff, once Tower issued the takeoff clearance to SW, he may have realized he made a mistake, but Hoped, Southwest would make a quick takeoff and no harm no foul.

Sometimes, my F/O will call Tower to state we’re holding #1 for takeoff even though we both see there is arriving traffic on final. I will speak up now to remind them, a Holding #1 call is not necessary and serves no purpose most of the time.
Vito is offline  
Old 02-09-2023, 05:58 AM
  #79  
Gets Weekends Off
 
Joined APC: Jan 2014
Posts: 1,890
Default

Originally Posted by Vito View Post
Spoiler
 
I’ll throw this out there for discussion. SouthWest’s call to Tower, stating “Southwest Holding short Rwy 18L , we’re ready” was totally unnecessary and One can argue was the catalyst of this entire incident.

Number One, Why make that call? Who cares?. It accomplished nothing except to clog up the Tower freq with unnecessary chatter while another aircraft is attempting to fly a Cat 3 approach.

Number 2, This call prompted the Tower controller to issue a dubious takeoff clearance, which, if the call was never made, the Takeoff clearance would never have been issued.

Number 3, it set up a situation where SW had to rush his takeoff roll, if he were even aware enough to realize how close FedEx was.
And this call possibly caused Tower, out of habit, to clear SW for takeoff, once Tower issued the takeoff clearance to SW, he may have realized he made a mistake, but Hoped, Southwest would make a quick takeoff and no harm no foul.

Sometimes, my F/O will call Tower to state we’re holding #1 for takeoff even though we both see there is arriving traffic on final. I will speak up now to remind them, a Holding #1 call is not necessary and serves no purpose most of the time.
I generally agree except in my experience smaller airport towers seem to wait for you to check in at the end of the runway while larger airports don’t (which likely includes AUS).
Gspeed is offline  
Old 02-09-2023, 06:44 AM
  #80  
Gets Weekends Off
 
Joined APC: Oct 2015
Posts: 711
Default

Originally Posted by Vito View Post
Spoiler
 
I’ll throw this out there for discussion. SouthWest’s call to Tower, stating “Southwest Holding short Rwy 18L , we’re ready” was totally unnecessary and One can argue was the catalyst of this entire incident.

Number One, Why make that call? Who cares?. It accomplished nothing except to clog up the Tower freq with unnecessary chatter while another aircraft is attempting to fly a Cat 3 approach.

Number 2, This call prompted the Tower controller to issue a dubious takeoff clearance, which, if the call was never made, the Takeoff clearance would never have been issued.

Number 3, it set up a situation where SW had to rush his takeoff roll, if he were even aware enough to realize how close FedEx was.
And this call possibly caused Tower, out of habit, to clear SW for takeoff, once Tower issued the takeoff clearance to SW, he may have realized he made a mistake, but Hoped, Southwest would make a quick takeoff and no harm no foul.

Sometimes, my F/O will call Tower to state we’re holding #1 for takeoff even though we both see there is arriving traffic on final. I will speak up now to remind them, a Holding #1 call is not necessary and serves no purpose most of the time.
I was taking off out of AUS the day after this happened with low IFR. They asked us to report holding short of 18L. I assume this is what happened with SW as well.. Adding the “we are ready to go” might not have been necessary, but I would by no means call it the catalyst for the whole situation.
Broncofan is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
firstmob
Delta
60
12-18-2023 12:11 PM
Overnitefr8
Cargo
3
05-21-2008 12:15 PM
Runner
Major
2
02-20-2008 02:57 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices