Why should I file altitude changes unless there is a good reason to?
Often, these are required to get the route to validate. One almost never has to fly the vertical changes though.
Before Autorouter, I used FlightPlanPro and that didn’t operate any kind of aircraft performance model for the purpose of developing the route. It still came up with much the same routes as Autorouter does, especially in terms of what is actually flown. FPP did generate loads of level changes too but they were for validation purposes only. However I think FPP (which was always my backup) is now broken; not much validates except France.
Often, these are required to get the route to validate.
Well, that is a good reason But often the route will still validate even if you remove some of those.
In the case of FPP that would not normally validate i.e. it changes levels only to get validation. With Autorouter, quite possibly yes because AFAIK it changes the levels according to a/c perf.
The one thing I wish I knew how to tweak is taxi/run-up time.
They come from a Eurocontrol database of expected taxi times for each airport. It’s a delicate subject because certain airlines would cheat on the taxi times to get ahead of the slot queue. Eurocontrol ask us to not allow anybody to deviate.
It’s a delicate subject because certain airlines would cheat on the taxi times to get ahead of the slot queue. Eurocontrol ask us to not allow anybody to deviate.
This brings up another question slightly off topic: how is the taxi time used and how important is it? Does it matter at all unless flying from airports with flow control?
At most airfields I fly, the taxi time seems to be set at 5 minutes whereas I seem not to be able to get ready for take-off in less than 10 minutes, taxi and run-up included.
Prob with outdated TAFs in autorouter
Autorouter sends outdated TAFs for a lot of French and Swiss airports right now, all seemed stuck to 23 June 1400Z or 1700Z, or little more.
From other sources, they’re up to date.
Metars are ok.
The Autorouter wx bot will send you yesterday’s wx, if the airport has not yet reported. For example, just now:
EGKA 241850Z 24019G29KT 8000 3500SE VCFG FEW001 BKN005 17/16 Q1013
TAF AMD EGKA 241530Z 2415/2418 24015KT 6000 BKN006 TEMPO 2415/2418 24018G28KT 4000 -RADZ BR BKN003 PROB30 TEMPO 2415/2418 1400 DZ
EGKA won’t have wx info for a few more hours today…
It is a perfect example of why one should check the date on metars and tafs.
However your example is 2 days old, no? That’s odd.
The problem is caused by the data source NOAA (US FAA source). I have reported it, thanks for the heads up.
The issue was resolved by NOAA.
I have just (0655 on 29/6) done a NEAR EGBT in Telegram and got:
Nearest weather stations:
EGTK – Kidlington 14NM SW
EGTK 290620Z 31008KT 9999 FEW011 BKN022 OVC027 11/09 Q0994
TAF EGTK 290553Z 2906/2915 32008KT 9000 SCT016 BECMG 2906/2909 9999
EGTC – Cranfield 17NM E
EGTC 290620Z 27007KT 230V300 9999 BKN008 11/10 Q0993
TAF EGTC 281401Z 2815/2818 34008KT 9999 BKN007 TEMPO 2815/2818 4000 -RADZ BKN010 PROB30 TEMPO 2815/2818 BKN015
EGBE – Coventry 24NM NW
EGBE 281550Z 36009KT 330V030 9999 BKN013 14/12 Q0998
TAF EGBE 281358Z 2815/2824 01007KT 9999 BKN010 PROB30 TEMPO 2815/2824 BKN008
EGVN – Brize Norton AB 25NM SW
EGVN 290550Z 31009KT 9999 SCT012 BKN030 11/09 Q0995 GRN TEMPO FEW012 BLU
TAF EGVN 290446Z 2906/3006 31006KT 9999 SCT030 PROB40 TEMPO 2906/2909 BKN012 TEMPO 2909/2913 SCT020 PROB30 TEMPO 2916/2919 7000 SHRA SCT022 TEMPO 2923/3006 BKN020 PROB30 TEMPO 3000/3006 7000 -RA SCT010
EGUB – Benson 25NM S
EGUB 290550Z 29006KT 9999 BKN011 12/09 Q0994 GRN NOSIG
TAF COR EGUB 290449Z 2906/2915 30005KT 9999 FEW012 BKN035 TEMPO 2906/2909 SCT012 TEMPO 2909/2912 SCT020
EGGW – London Luton 28NM ESE
EGGW 290620Z AUTO 28009KT 9999 OVC008 11/10 Q0994
TAF EGGW 290453Z 2906/3006 28007KT 9999 OVC010 TEMPO 2906/2908 OVC008 BECMG 2909/2912 SCT030 PROB30 TEMPO 2917/2924 9000 -SHRA BKN014 PROB30 TEMPO 3002/3006 7000 BKN004
EGVA – Fairford 33NM SW
EGVA 290558Z AUTO 30009KT 9999 OVC030 11/09 A2938 RMK AO2 SLP952 T01140087 10122 20107 55003
EGBB – Birmingham 34NM NW
EGBB 290620Z 30009KT 9999 BKN009 OVC022 11/10 Q0994
TAF EGBB 290455Z 2906/3006 31009KT 9999 SCT018 TEMPO 2906/3006 BKN010 PROB30 TEMPO 2906/2910 BKN006 PROB40 TEMPO 2918/3006 4000 RADZ BR FEW002 BKN005
EGWU – Northolt 38NM SE
EGWU 290550Z 29006KT 9999 SCT013 OVC032 12/09 Q0994 GRN TEMPO FEW013 BLU
TAF EGWU 290432Z 2906/2924 30006KT 9999 BKN035 TEMPO 2906/2912 SCT018 PROB30 TEMPO 2906/2908 SCT014
Scanning down, you see that that weather at Luton is nice enough, but it’s pretty shit at Cranfield, which is only 15nm away and 200’ lower.
Until you look a little closer The same is true of Coventry.
I don’t think that the issue has gone away.