PDA

View Full Version : Pilots/ATC - What assistance do you expect in an RTO?


safety_worker
25th Nov 2001, 23:10
Just the other day I witnessed an RTO (medium speed :) ). The amount of questions being asked by ATC to the pilot, and obviously not in 'any' distress, the amount of time taken by the pilot(s) to answer him, makes me ask questions. It is posed mainly to our ATC friends, but I'd like to know what your (pilots) ATC friends think (if you get any views) and what your views are?
My ATC friend says, he wouln't hit the crash button if it was a 'low-speed RTO'. His concern was mainly a 'high-speed RTO' because of possiblity of brake fires. Good point. My further question was, could a low-speed RTO be due to an Engine-Fire? "Hmm, yeah, I suppose you're right" - Not the point.....
1. What does ATC have in their SOPs for an RTO?
2. Why all the questions? We had an RTO, not an everyday occurence. Why not hit the 'crash button' ask questions later? Give us pilots time to sort out the problem we had, that caused the RTO!
3. What do we pilots expect ATC to do?
4. Would/Should we call a MayDay if we RTO-ed for an Engine Fire?
Needless to say, we're looking into SOPs all the time to make them better - (Risk Management?).
Ta and Safe Bidings!

BmPilot21
26th Nov 2001, 00:16
The correct R/T for an RTO is 'birdseed 121 stopping', you may add 'engine fire etc' to that if relevent. I might also say 'request full assistance' if I needed it.

I stopped the other day for a config. warning, and said 'xxx stopping, no assistance required' which I think atc were grateful for as it saves them asking. We wouldn't have wanted him to hit the crash button for that!

Hope this helps.

Spoonbill
26th Nov 2001, 00:35
Unless there is an obvious visible need for further assistance, or there is no two way communication with the aircraft in question within a reasonable amount of time, we simply ask the pilot if they require further assistance.
Saves a lot of hassle.

safety_worker
26th Nov 2001, 07:21
We don't always 'know' at the time of completion of the RTO if assistance is required. We can't see brakes/tyres, (ATC in LVP?), we have to deal with the 'reason' that caused the RTO first. Some situations are obviously leading to an Evacuation- gear collapse, but for a situation with so many variables, does ATC have 'one standard'?
Just curious what ATCs SOP is in RTO.
How often is there an RTO and besides wouldn't it help the 'procedures' and ATC 'quality assuarance' evaluate the 'real drill'?
If the aircraft needs the assistance, its there!

GoneWest
26th Nov 2001, 08:47
Can there be a STANDARD O.P. (S.O.P.) to a non-standard event??

I landed one night at Manchester, in a light twin (PA31). Controller saw my navigation lights turning off the runway - used "anticipated seperation" to clear Birdseed123 for departure - my right brake seized and the aircraft spun round...back onto the runway in front of a 737 that was just commencing its take off roll.

I shouted "Birdseed - abandon take off" on the R/T, (actually didn't get his flight number - just the Company).

How would you expect ATC to handle it???

All controller efforts were put into a sudden string of "go around"s.

safety_worker
26th Nov 2001, 14:05
SOP's do cater for 'events', though not all. When we have a non-normal in the aircraft, we use SOP's. In an incomprehensible and unknown situation we use our judgement based on various factors (knowledge, skills and experience, among others) to arrive at the safest result. I am sure ATC does the same.
I am interested in ATC's 'Cheklist' or SOP for an RTO, which is a Non-Normal situation ;)

U R NumberOne
26th Nov 2001, 15:00
If only things were so orderly in our world that a checklist could be produced for things like an RTO or any other emergency. Controllers know their responsibilities and know which tools their have at their disposal to assist in handling the problem. How we get from the start of the incident to (hopefully) a successful conclusion is down to the individual ATCO taking all the factors into account and dealing with it in what they consider to be the best way. No checklist - just making it up as we go along (nothing new there anyway :D )

As mentioned above, if the crew can say something like "no assistance required" or if there's any possibility of something serious occuring "request assistance", that would greatly help us in making the most critical decision (AFS callout or not), and stops us having to trouble you at a time when flightdeck workload is very high. So a quick call like that can save all concerned a great deal of hassle.

[ 26 November 2001: Message edited by: U R NumberOne ]

Gonzo
26th Nov 2001, 23:03
Basically we need to know if emergency assistance is required, and also the reason for abandoning to determine whether a runway inspection is required.

From our Manual of Air Traffic Services Part. 1: "Additional surface inspections should be made: .....following an abandoned take off by a turbine engined aircraft due to an engine malfaunction, or by any aircraft due to burst tyres........or when considered necessary by ATC.

Gonzo.