Adding LFXX and EHXX Stations to EBBU Profiles#451
Conversation
DEC is still missing
LFQQ APP still needs to be decided how to implement
Added AMS S and LFQQ QE
LFQQ APP needs to be decided how to implement
Remove LFQQ Button
Split LFQQ Buttons to E and W
DEC is not callable yet
NichoAir
left a comment
NichoAir
left a comment
There was a problem hiding this comment.
Remove empty line
Remove empty String
| }, | ||
| { | ||
| "label": ["LFQQ"] | ||
| "label": ["LFQQ"], |
There was a problem hiding this comment.
Can we make the label LFQQ E? As it is IRL on the EBBR APP profile
| "label": ["AMS", "S"], | ||
| "color": "clay" | ||
| "color": "clay", | ||
| "station_id": "EHAA_S" |
There was a problem hiding this comment.
I see EHAA E is missing, is that on purpose? EHAA E is there on the east profile IRL.
Adding "E" to LFQQ in EBBR APP
|
AMS E added and LFQQ changed to LFQQ E for EBBR APP |
@JanWillemOomes AMS East is not connected to our Airspace, EHMC is in between, that is why I didn't add East |
Little oepsie from me. IRL they can call AMS E, AMS N E, AMS R7. With AMS E being executive, not east haha. I think its best if we set up: EHAA S -> AMS S (123.850) And not to forget Maastricht Approach -> BEEK APP (if its not in there already, if not also needs to be added to the EBBU APP profile). EHAA east is indeed not necessary. IRL New Mil TMA D only goes up to FL195 with FL195-FL245 being covered by AMS S, looks like they simplified its simulation on VATSIM and let it go up to FL245. |
2 participants
Adding EHAA Station IDs to EBBU APP, EBBU CTR and EBBR APP Profiles
Adding LFXX Station IDs to EBBU APP, EBBU CTR and EBBR APP Profiles
Adding 2nd LFQQ Button to EBBU CTR Profile
Remove LFQQ button from EBBU APP Profile