Since the arrival of ATIS on Expert, I have been following the “straight out departures only” instruction by flying the runway heading until reaching the last of the blue circles indicating the airport’s airspace (after announcing a straight out departure when requesting take off clearance).
However, I have noticed a lot of other aircraft making immediate turns after rotation without any comeback from the Tower, so am just wondering how rigid this ATIS instruction actually is.
The following happened to me on departure from WSSS 02C just now, but I think this may have been more to do with poor parallel runway etiquette by the other pilot climbing off 02L (guessing he should have turned left to aim for Jakarta, or just waited until I had turned). Still, had the straight out departure thing that was being broadcast on the ATIS been observed then this wouldn’t have been an issue.
The problem is that a lot of people don’t know what Straight Out Departure actually means (although it should be self explaining…)
If a pilot is cleared for Straight Out though he’s not allowed to do such a turn right away. He’s not following the instructions which is a ghosting reason.
Just report the pilot if he’s obviously disregard the instructions. He should not turn if you’re still there. Collisions aren’t very healthy for planes.
I also hear on the Tower frequency lots of “departing south” type of announcements that do not get a Check Help in response, so to be honest I think this is partly on some of the controllers to enforce if they have set a straight out requirement on the ATIS. If they don’t care about people turning 30 feet beyond the end of the runway then it’s probably best not to put that on ATIS to start with.
In all honesty we had been pretty forgiving as ATIS is new. That will start changing over time however. They may not be ghosted, but they should be told to check ATIS information, and the help pages. If they interfere with other aircraft however they should be immediately ghosted.
I do send check ATIS and check help pages and if they insist on doing it, I tell them to extend upwind and then please follow instructions. If they interfere with others, I ghost them immediately.
Like @Brandon_Sandstrom said, it’s new and everyone is learning. It’s not like they can learn it on the training server. Over time, we will enforce it more and more.
Straight out departures aren’t a new thing that came out with the update, everyone flying on the expert server should know how to execute a straight out departure on Unicom or in a controlled airspace. There is really no excuse. It is sort of idiot proof, straight out departures only, plan on performing a straight out departure because that’s the only thing that is accepted when it’s included.
Many of them should know what straight out departures are. Before ATIS, I had several people state departing straight out and they started banking right after rotation. They need to educate themselves on this. I think it will get their attention when we start ghosting them for this.
If I understand you correctly: IFATC want pilots to call a straight out departure even if our flightplan goes east/west/north/south? Given that ATIS say «straight out departures only»
This is at the end of the ILS or GPS approaches (so if departing, stay runway heading until out of the approaches of the runway in the opposite direction)
If you see someone not following instructions as a pilot be patient, the controller is never not multitasking, it can take time to find and click check help pages, but someone will get to it. Sometimes if I have to handoff to someone else (approach/departure) I won’t bother clicking check help because it takes up too much of my time and the handoff timing is more important. We are in constant communication via chat channels so just keep that in mind, they may get check help when they switch to the other frequency.
You don’t exactly use the cones and you are supposed to maintain runway heading. Read the topic below to understand how parallel runway departures should work.
This brings up the case for SID and STAR procedures in the future. My VA uses them exclusively and when it’s a vectoring situation off a specific climb pattern (JFK Canarsie Climb for example) we track the real world departures to ensure a properly flown departure that won’t get in the way of inbound traffic.
If you want to come learn how to fly them with some help, come on down to VirtualBlue VA Site and join up.
There’s plenty of guys around that’ll be able to help you read and show you how to fly the charts by the numbers. I just finished doing one on the Expressway Visual to 31 at KLGA and we’ll be doing a group flight to show how the ROBUC3 (and part of the older KRANN3 due to IF Nav issues) work out for spacing.
