08.01.2015 Views

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

210<br />

AFMAN 11-217V1 3 JANUARY 2005<br />

restrictions are omitted, those altitude restrictions are canceled, including<br />

SID/DP/STAR altitude restrictions.<br />

9.8.5.4.1. An Example. ATC initially gives you the following clearance: “Track<br />

32, cross Ollis intersection at or above 3,000; Gordonsville VOR at or above<br />

12,000; maintain FL 200.” Shortly after departure, the controller changes the<br />

altitude to be maintained to FL240. If the controller wants you to continue to<br />

comply with the previously issued altitude restrictions, he will restate them like<br />

this: “Track 32, amend your altitude. Cross Ollis at or above three thousand;<br />

cross Gordonsville at or above one two thousand; maintain flight level two four<br />

zero.” If he wants you to climb unrestricted to FL 240 and disregard the<br />

previously issued altitude restrictions, he will issue the following clearance:<br />

“Track 32, climb and maintain flight level two four zero."<br />

9.8.5.4.1.1. CAUTION: It is important to understand the different types of<br />

altitude restrictions that may be depicted on SIDs. Although you may be able<br />

to disregard ATC altitude restrictions after receiving an amended clearance,<br />

some altitude restrictions are depicted due to terrain and/or obstacles.<br />

Obviously, these types of restrictions can never be disregarded. If there is any<br />

question about your new clearance and/or the applicable altitude restrictions,<br />

query the controller.<br />

9.8.5.5 Restrictions Not Depicted On the SID. If it is necessary for the controller to<br />

assign a crossing altitude that differs from the SID altitude, the controller should<br />

repeat the changed altitude for emphasis. If you are radar vectored or cleared off an<br />

assigned SID, you may consider the SID canceled unless the controller adds “Expect<br />

to resume SID.” If ATC reinstates the SID and wishes any restrictions associated<br />

with the SID to still apply, the controller will state: “Comply with restrictions.”<br />

9.8.5.5.1. CAUTION: When pilots and controllers discuss changes to SIDs, the<br />

potential for miscommunication is high. If there is any question about your<br />

clearance, query the controller.<br />

9.9. Specific ATC Departure Instructions. Specific ATC departure instructions include a<br />

heading to fly and an altitude. Although a heading in normally associated with radar vectors,<br />

there are some situations when ATC’s departure instructions do not meet the strict definition<br />

of a “radar vector.” For example, prior to departure, tower may issue you the following<br />

clearance, “Track 32, on departure, turn right heading 360, climb and maintain 5,000 feet.”<br />

In this case, technically, this instruction is not a “radar vector” because it is not “navigational<br />

guidance based on the use of radar.” Even so, if you are operating in a radar environment,<br />

you are expected to associate departure headings with radar vectors to your planned route of<br />

flight. Although not as common as the example above, there are situations when ATC may<br />

give you specific departure instructions even when radar is not available.<br />

9.9.1. NOTE: Except in a DVA, you should fly the ODP prior to the radar vector. You<br />

must carefully review all aspects of FLIP to determine the appropriate actions. This is<br />

mainly apparent at airports with a “Trouble T” that states something similar to this, “All<br />

Departures climb to 1600 prior to any turns.” However, if there is any doubt, query ATC.<br />

9.9.2. The first thing you need to know about a radar departure is what the term, “radar

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!