Do you do a immediate turn after takeoff ? - #3 by anon57683537 By the way, it is called a localizer.
For me it depends on if I’m at a busy airport or not. For example I’m at LAX on Training Server I will fly the heading of the runway and go about 1 mile over the ocean then turn. If I’m at Salt Lake (SLC) I will turn immediately after getting off the ground.
No I don’t to do that. I like to carry on the runway heading for a little while and then start turning.
I always depart straight out. Usually past the ILS.
I usually go out a bit and then turn a little.
The spirit behind the “straight out departures” in the ATIS is more for parallel runways to prevent people from crossing into the paths of other aircraft. Most will get 0.5 feet off the ground and turn on NAV which makes the plane turn around most of the time and interfere.
For me, it depends on 2 things:
1. The SID I am following
2. The real life flight I am mimicking
This is one of the reasons why I don’t fly to IFATC areas very often because the airspace traffic can get unrealistic quickly.
For example, a standard SID from SFO Airport departing 1R is to takeoff, turn right, and fly over OAK before continuing toward your destination. Departing 1L, and heading south, you would normally depart, then turn left immediately and then head south. Due to the popularity of SFO in IF, many IFATC controllers add “straight out departures only” meaning I would have to fly runway heading until I reach the end of the cone before I can even think about turning, which is unrealistic.
Now, let’s take SJC into consideration. Whenever Tyler features SJC in the IFATC schedule, sometimes he adds airports alongside SJC for the same day but are not as popular as SJC. As a result of this, SJC is crowded for the day. Whenever an area is crowded, IFATC controllers like to put “straight out departures only.” This is especially unrealistic for SJC because every departure from SJC has to follow the right loop procedure. Departing straight out means you would directly interfere with SFO arrivals, making the departure in IF unrealistic.
Of course, IF airspaces can be different from real world airspaces so IFATC “can’t have realistic procedures” all the time. You can look at the thread below. This is the main reason why I don’t fly into IFATC areas very often.
Well no that’s what I do usually
Taking off from the taxiway? I thought it was when you take off from a runway that intersects with another (say KSFO).
I was at Heathrow to pick up a relative and saw many jets turn right after taking off. Looked pretty cool.
Not from the taxiway, but entering the runway from a taxiway midway down the runway.
So for example:
If you’re taking off from 12R, entering the runway from taxiway Charlie would be full-length.
If you were in a Cessna or something and entered the runway at Quebec or November, that would be an intersection departure.
It’s got nothing to do with taxiway midway down the runway.
That covers intersecting runways, not intersecting departures. They’re two different things.
@Alex_Kraz you have to keep in mind that in the FR24 map their turn may be 10-20 miles after taking off. The point is that they are not crossing over in front of the parallel runway. But it is very common.
Take for example my favorite JASPA5 SID out of KDFW. Upon take off they make a slight turn ro hit GVINE or MECHL.
There are take off notes for the initial climb out that state for runway 36R
Climb heading 356 to intercept course 338 to GVINE, then on course 262 to cross KMART at or above 550 and at or below 240 kt, then on depicted route to JASPA
I personally love turning after take off as it does help the realism. I just don’t make a hard 90 degree turn or cross over other runways while doing it.
But it specifically says intersecting runway departures.
Does ATC IRL usually stagger departures when this happens? I’ve always wondered if that’s how it works, when 2 parallels on a SID intersect at 1 waypoint.
This is one of the greatest comments I’ve ever read . Thank you Mr. Tim B