To sum up.
I think there is a procedural error here. If there is a standard departure guidance in the FAA's A/FD it should be the default rule.
Can ATC overrule it? Absolutely.
We are in agreement here. The A/FD departure procedure is the default and ATC can override it.
The "general guidance" to turn in the shortest direction has to be overridden by the specific A/FD departure guidance to turn left 15 degrees IMMMEDIATELY at the end of the runway. It's almost a dire warning
The A/FD does NOT say immediately. The exact quote of the procedure from the A/FD is :
Rwy 20L departures turn 15º left at departure end of rwy. To avoid overflights of Rwy 02L, Rwy 02R departures turn 15º right at freeway.
It's not a dire warning (which is what Immediately can mean), but simply a procedure to handle departures from close parallel runways.
I disagree with the overridden part of your statement. The Federal Regulations require the opposite.
(g) Departures. No person may operate an aircraft departing from an airport except in compliance with the following:
(1) Each pilot must comply with any departure procedures established for that airport by the FAA.
You can't simply take part of a regulation without looking at the whole regulation. I'll admit that I clipped non-relevant parts in my discussion, so here is the 100% complete 91.129 (which we have both posted from). I'll bold the parts we are both looking at to make it easier to read.
(a) General. Unless otherwise authorized or required by the ATC facility having jurisdiction over the Class D airspace area, each person operating an aircraft in Class D airspace must comply with the applicable provisions of this section. In addition, each person must comply with Secs. 91.126 and 91.127. For the purpose of this section, the primary airport is the airport for which the Class D airspace area is designated. A satellite airport is any other airport within the Class D airspace area.
(b) Deviations. An operator may deviate from any provision of this section under the provisions of an ATC authorization issued by the ATC facility having jurisdiction over the airspace concerned. ATC may authorize a deviation on a continuing basis or for an individual flight, as appropriate.
(c) Communications. Each person operating an aircraft in Class D airspace must meet the following two-way radio communications requirements:
(1) Arrival or through flight. Each person must establish two-way radio communications with the ATC facility (including foreign ATC in the case of foreign airspace designated in the United States) providing air traffic services prior to entering that airspace and thereafter maintain those
communications while within that airspace.
(2) Departing flight. Each person--
(i) From the primary airport or satellite airport with an operating control tower must establish and maintain two-way radio communications with the control tower, and thereafter as instructed by ATC while operating in the Class D airspace area; or
(ii) From a satellite airport without an operating control tower, must establish and maintain two-way radio communications with the ATC facility having jurisdiction over the Class D airspace area as soon as practicable after departing.
(d) Communications failure. Each person who operates an aircraft in a Class D airspace area must maintain two-way radio communications with the ATC facility having jurisdiction over that area.
(1) If the aircraft radio fails in flight under IFR, the pilot must comply with Sec. 91.185 of the part.
(2) If the aircraft radio fails in flight under VFR, the pilot in command may operate that aircraft and land if--
(i) Weather conditions are at or above basic VFR weather minimums;
(ii) Visual contact with the tower is maintained; and
(iii) A clearance to land is received.
[(e) Minimum altitudes when operating to an airport in Class D airspace. (1) Unless required by the applicable distance-from-cloud criteria, each pilot operating a large or turbine-powered airplane must enter the traffic pattern at an altitude of at least 1,500 feet above the elevation of the airport and maintain at least 1,500 feet until further descent is required for a safe landing.
(2) Each pilot operating a large or turbine-powered airplane approaching to land on a runway served by an instrument approach procedure with vertical guidance, if the airplane is so equipped, must:
(i) Operate that airplane at an altitude at or above the glide path between the published final approach fix and the decision altitude (DA), or decision height (DH), as applicable; or
(ii) If compliance with the applicable distance-from-cloud criteria requires glide path interception closer in, operate that airplane at or above the glide path, between the point of interception of glide path and the DA or the DH.
(3) Each pilot operating an airplane approaching to land on a runway served by a visual approach slope indicator must maintain an altitude at or above the glide path until a lower altitude is necessary for a safe landing.
(4) Paragraphs (e)(2) and (e)(3) of this section do not prohibit normal bracketing maneuvers above or below the glide path that are conducted for the purpose of remaining on the glide path.]
(f) Approaches. Except when conducting a circling approach under Part 97 of this chapter or unless otherwise required by ATC, each pilot must--
(1) Circle the airport to the left, if operating an airplane; or
(2) Avoid the flow of fixed-wing aircraft, if operating a helicopter.
(g) Departures. No person may operate an aircraft departing from an airport except in compliance with the following:
(1) Each pilot must comply with any departure procedures established for that airport by the FAA.
(2) Unless otherwise required by the prescribed departure procedure for that airport or the applicable distance from clouds criteria, each pilot of a turbine-powered airplane and each pilot of a large airplane must climb to an altitude of 1,500 feet above the surface as rapidly as practicable.
(h) Noise abatement. Where a formal runway use program has been established by the FAA, each pilot of a large or turbine-powered airplane assigned a noise abatement runway by ATC must use that runway. However, consistent with the final authority of the pilot in command concerning the safe operation of the aircraft as prescribed in Sec. 91.3(a), ATC may assign a different runway if requested by the pilot in the interest of safety.
(i) Takeoff, landing, taxi clearance. No person may, at any airport with an operating control tower, operate an aircraft on a runway or taxiway, or take off or land an aircraft, unless an appropriate clearance is received from ATC. A clearance to "taxi to" the takeoff runway assigned to the aircraft is not a clearance to cross that assigned takeoff runway, or to taxi on that
runway at any point, but is a clearance to cross other runways that intersect the taxi route to that assigned takeoff runway. A clearance to "taxi to" any point other than an assigned takeoff runway is clearance to cross all runways that intersect the taxi route to that point.
Note part a. It says that compliance with this section is mandatory UNLESS otherwise authorized or required by ATC. Receiving a heading from ATC constituents a requirement per 91.123 (listed below).
(a) When an ATC clearance has been obtained, no pilot in command may deviate from that clearance unless an amended clearance is obtained, an emergency exists, or the deviation is in response to a traffic alert and collision avoidance system resolution advisory. However, except in Class A airspace, a pilot may cancel an IFR flight plan if the operation is being conducted in VFR weather conditions. When a pilot is uncertain of an ATC clearance, that pilot shall immediately request clarification from ATC.
(b) Except in an emergency, no person may operate an aircraft contrary to an ATC instruction in an area in which air traffic control is exercised.
(c) Each pilot in command who, in an emergency, or in response to a traffic alert and collision avoidance system resolution advisory, deviates from an ATC clearance or instruction shall notify ATC of that deviation as soon as possible.
(d) Each pilot in command who (though not deviating from a rule of this subpart) is given priority by ATC in an emergency, shall submit a detailed report of that emergency within 48 hours to the manager of that ATC facility, if requested by ATC.
(e) Unless otherwise authorized by ATC, no person operating an aircraft may operate that aircraft according to any clearance or instruction that has been issued to the pilot of another aircraft for radar air traffic control purposes
So, if it doesn't apply, Why doesn't the FAA A/FD carry the same weight as an FAA Approach Plate or SID?
Simply put because the A/FD is not part of the regulations while FAA instrument procedures are. FAA instrument procedures are governed by part 97 of the FARs. Within part 97 you will find this in 97.20 (b):
Standard instrument procedures are associated supporting data adopted by the FAA and documented on FAA Forms 8260-3, 8260-4, 8260-5. Weather takeoff minimums are documented on FAA form 8260-15A. These forms are incorporated by reference. [clipped approval to do this and several reg citations allowing it]
Form 8260 relates to the establishment of various instrument procedures. Specifically:
8260-3 = Instrument Approach Procedure (Precision)
8260-4 = Instrument Approach Procedure (Radar)
8260-5 = Instrument Approach Procedure (Non-Precision)
8260-15A = FAA Obstacle Departure Procedures
You'll find no incorporation of the A/FD into federal regulations. Should you follow A/FD guidance, YES. Does it overrule federal regulations requiring otherwise, No. Here's another example of where ATC can overrule the A/FD. The A/FD for SNA says to make left closed traffic for runway 20L, I think we can agree that if ATC says to fly right closed traffic for runway 20L that this would overrule the A/FD.
Also - to me - turning left 15 degrees before turning RIGHT back to 330 is like trying to be 1/2 pregnant. Doesn't make any sense. If the purpose of the A/FD directive is to avoid overflying the parallel runway then turning left 15 degrees for 30 seconds doesn't make any difference -- 300 AGL vs 600AGL etc.
I agree, it is a bit silly. It would ensure compliance with both the A/FD and ATC at the appropriate points, but otherwise doesn't help things.
At a minimum I would expect ATC to AMEND the standard departure (turn left 15 deg) or to direct pilots to Turn RIGHT to 330 (overrulling standard departure procedure). They gave no guidance at all and the only guidance extant was the turn left immediately at departure end of the runway. The turn left HAS to be the default...
The ATC handbook (FAA Order 7110.65) doesn't require this. Per the Pilot Controller Glossary if no direction is specified you should turn in the quickest direction. The reason we don't specify direction is in case of a runway switch.
The purpose of the Pilot Controller Glossary is:
This Glossary was compiled to promote a common understanding of the terms used in the Air Traffic Control system.
While not required to be used by pilots (note that it is part of the AIM which states "The AIM is made available solely to assist pilots in executing their responsibility as required by other publications"), it IS required to be used by controllers (as it is included in FAA Order 7110.65 which is mandatory for controllers to comply with). Therefore following that guidance will constitute complying with an ATC clearance as required by FAR 91.123. Note that FAR 91.123 stated that if there is confusion over a clearance you should clarify that with ATC. In this case if you aren't sure which way to turn ask ATC and we will let you know.
To answer the couple of other questions I didn't get to in the main part of my reply:
what the heck constitutes governing ATC?
I'm not sure what you are asking here.
And why would the FAA published Airport/Facilities Directory which contains various wonderful and mandatory information suddenly become optional
It's not mandatory as it's not a regulation. Note that a couple parts of the A/FD are mandatory because they are repeated in various regulations (this mainly relates to traffic pattern direction), other parts are needed to comply with other regulations (such as runway distances), and other parts are on topics that the FAA doesn't choose to regulate (such as the hours when fuel is provided at an airport). Note that I am NOT saying don't use the A/FD (I think it's a great tool that's underutilized), just that it's not the end all be all.
Generally the A/FD doesn't include things that require "compliance" from a pilot (except as noted above),. This departure procedure is a bit of an anomaly to be honest (which is why there isn't really a clear answer in all of this). The NTSB website is acting up or else I'd try to find you a legal decision on all of this.
This isn't some pub thrown together by the airport manager on a Saturday - it comes from the FAA
Comes from the FAA and being made by the FAA are separate things. Most information in a A/FD comes from the airport manager and is simply compiled by the FAA. From the legend:
This directory is a listing of data on record with the FAA on public–use airports, military airports and selected private–use airports
specifically requested by the Department of Defense (DoD) for which a DoD Instrument Approach Procedure has been published in the
U.S. Terminal Procedures Publication.
But I'm a low time PPL with no cloud card and will of course yield to higher authority...reluctantly
Nothing wrong with asking questions. So you know who I am beyond the PE QA guy, my flying based credentials are an ATP with ratings in AMEL, ASEL, ASES, Glider (and a type rating in everyone's favorite* airliner, the CRJ). I'm also a gold seal CFI/II/MEI (with a little over 2000 hours dual given in aircraft and FTD's), I've also been a part 141 check instructor. Note that doesn't mean I'm right, make your own judgement based on what I posted above.
Please post if you have more questions/comments.
* - May not be true