37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1383144 |
Time | |
Date | 201608 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | IAD.Airport |
State Reference | DC |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Route In Use | SID BUNZZ3 |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 9832 Flight Crew Type 6769 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Our data link clearance was climb via bunzz 3 RNAV SID. Upon reaching the runway the tower controller issued the takeoff clearance along with change to the SID; 'fly runway heading' (which is what is specified in the SID) without also issuing an altitude. [Company] flight operations manual (fom) specifically states 'however; if tower then simply issues a heading to fly on departure; an altitude should be included with the heading since the SID climb via clearance has been replaced by the heading assignment.' I understand FAA control facilities do not operate by [my company's] fom; but it is very carefully distilled from FAA documents and procedures. I don't know what the actual source is. I do know people at [my company] didn't make it up.I spoke with a supervisor at iad tower yesterday who did not agree that this is the case so I feel the issue should be followed up officially and decided. I also feel there are unnecessary threats and degradations to safety being created by either potomac approach and/or dulles tower in the issuance of RNAV SID's that are not being used as designed. I pointed out that the heading issued by iad tower is at least 9 times out of 10 redundant to the published SID. That is to say; it is exactly what is called for on the SID. The supervisor did not agree with my assessment of this either and when I suggested it would be easier and less confusing to allow flights to fly the SID's without the heading assignment; I was told that would never happen at dulles.so the reason there is a threat here is because dulles is issuing clearances that are simple to understand and replacing them at the last moment; literally as a flight is lining up to takeoff with something that because it's a change (they are saying the words after all) which gets ones attention yet is not a change at all. That causes confusion. Additionally the clearance is actually in error since it is technically a change (even though it really isn't) and should have an altitude assignment associated with it; but it doesn't. Lots of opportunity to get confused and make an error.lastly; this is all supposed to be a precursor and first steps of nextgen. What good will all the time; expense; and effort of nextgen be if a major facility like dulles and potomac can arbitrarily write their own rules and disregard what the rest of the country is doing?
Original NASA ASRS Text
Title: Air carrier Captain reported he received a non-standard clearance issued at takeoff by IAD Tower creating confusion among the flight crew.
Narrative: Our data link clearance was climb via BUNZZ 3 RNAV SID. Upon reaching the runway the tower controller issued the takeoff clearance along with change to the SID; 'fly runway heading' (which is what is specified in the SID) without also issuing an altitude. [Company] Flight Operations Manual (FOM) specifically states 'However; if Tower then simply issues a heading to fly on departure; an altitude should be included with the heading since the SID climb via clearance has been replaced by the heading assignment.' I understand FAA control facilities do not operate by [my company's] FOM; but it is very carefully distilled from FAA documents and procedures. I don't know what the actual source is. I do know people at [my company] didn't make it up.I spoke with a supervisor at IAD tower yesterday who did not agree that this is the case so I feel the issue should be followed up officially and decided. I also feel there are unnecessary threats and degradations to safety being created by either Potomac Approach and/or Dulles tower in the issuance of RNAV SID's that are not being used as designed. I pointed out that the heading issued by IAD tower is at least 9 times out of 10 redundant to the published SID. That is to say; it is exactly what is called for on the SID. The supervisor did not agree with my assessment of this either and when I suggested it would be easier and less confusing to allow flights to fly the SID's without the heading assignment; I was told that would never happen at Dulles.So the reason there is a threat here is because Dulles is issuing clearances that are simple to understand and replacing them at the last moment; literally as a flight is lining up to takeoff with something that because it's a change (they are saying the words after all) which gets ones attention yet is not a change at all. That causes confusion. Additionally the clearance is actually in error since it is technically a change (even though it really isn't) and should have an altitude assignment associated with it; but it doesn't. Lots of opportunity to get confused and make an error.Lastly; this is all supposed to be a precursor and first steps of NextGen. What good will all the time; expense; and effort of NextGen be if a major facility like Dulles and Potomac can arbitrarily write their own rules and disregard what the rest of the country is doing?
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.