CFMU Slot Allocation

[ghost-rider]

If we've been issued a CTOT, which we then discover we won't make, we'll delay the flightplan ( FPL ) or send an SRR ( Slot Revision Request ).

Now if we have to delay a FPL for whatever reason at the last minute, ie pax / baggage discrepancy, in other words something that couldn't have been foreseen in advance, unlike a late-inbound, why is it we're then classed by the CFMU system as a 'Late Updater'. <img src="confused.gif" border="0">

This means we are sent to the bottom of the queue if there's heavy restrictions on that route etc, and summariliy shafted by BRU/PAR ?!? <img src="eek.gif" border="0"> Goodbye schedule, goodbye crews due FTLs, goodbye on-time performance etc etc ! <img src="rolleyes.gif" border="0">

Surely if we're playing the game correctly, we should be allocated the next available slot ?

Don't get me wrong, if we miss a slot, and delay AFTER the original has expired then no arguments, but if we're doing all this in advance ?!? <img src="frown.gif" border="0">

No-one I've spoken to at CFMU seems to know why - and blame it on the system itself ! <img src="rolleyes.gif" border="0">

Anyone in the know shed any light as to the whys and wherefores ? <img src="confused.gif" border="0">

[ 19 February 2002: Message edited by: ghost-rider ]</p>

[cossack]

I think I have experienced what you describe.. .The FPL is delayed by an SRR and then a new CTOT way into the future appears. When you send a REA message, the CTOT usually comes forward nearer to what is required. . .I don't know why it happens this way but the crews are always appreciative having been given a big delay to have it reduced fairly quickly. <img src="smile.gif" border="0"> . .It would seem to be more logical to give you a CTOT that relates to your new requested EOBT without the need for a REA message, but who said anything about being logical? <img src="wink.gif" border="0"> <img src="confused.gif" border="0">

[ghost-rider]

Cossack & Rescue3,

Thanks for the replies ...

Just to give some examples :

Slot time 1300z. At 1255z we may get a call advising us of baggage ID, tech snag etc etc. . .SRR sent to BRU advising new EOBT at 1258z. Result - new CTOT based on new EOBT but classed as LU ( late updater ). If we get hammered with a bad slot, and ask BRU for help, we often get the response 'you are a late updater !'

Another eg : Flight plan expires at 1300z ( no slot issued ). Call received at 1245z saying same as above. etc etc. DLA msg sent with revised EOBT, and a slot comes in hammering us because the new EOBT puts the flight into a restriction - same response from BRU.

Now, if we MISS the slot and hadn't sent a DLA/SRR until after initial slot expiry - then fair comment, we'd send a SMM ( slot missed msg ) and close our eyes and pray!

But the examples above are indicative of what happens even though we are updating our EOBT with a SRR/DLA ** BEFORE ** the original slot or flight plan expiry, not after.

LU means we go to the bottom of the pile as far as I can tell !

The REA msg can only be initiated by ATC units, and as you say, can act as a 'get out of jail card'. But no use until the a/c is literally 'ready' for obvious reasons. The reason for this is the BRU computer will automatically allocate REA flights priority for improvements.

The whole point of all of this is to try and establish why (if?) flights in these circumstances get sent to the bottom of the pile and accordingly shafted when as I see it, we're playing the game by the rules and not trying to manipulate the system !

[ 21 February 2002: Message edited by: ghost-rider ]</p>