37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1411996 |
Time | |
Date | 201612 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | IAH.Airport |
State Reference | TX |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 19003 Flight Crew Type 2244 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
The most recent issue of NASA's ASRS newsletter was dedicated to this same issue of confusing controller pilot data link communications (cpdlc) clearances given at the departing airport. Multiple times in the past month I have received a revised clearance. Every time; the format used by the FAA interjects superfluous; ambiguous and contradictory information into the clearance that introduces confusion and uncertainty rather than a definitive; easily understood change.cleared to cnx viaroute clearance via todirect CRGERN3026.9 W9820.5+load new route to cnx+ aftercnx cleared to ZZZ airport as FILEDPITZZ4. Crger.....we are not cleared to cnx; we are cleared to ZZZ; but you have to go 7 lines down to see that… it says 'direct crger;' but indeed we are not cleared direct to crger; but via the PITZZ4 departure...then there is a coordinate given. Is this an additional point? This does not match the coordinates for crger in either our navigation database; nor our jeppfd-pro. All of the additional information issued in via the cpdlc only confuses the issue. The first 8 lines of the routing info in on the clearance should be deleted. It would be clear; unambiguous and not contradictory to simply say:revised routing:PITTZ4 crger as filedno confusion; no contradictions; no mismatched databases. Completely understandable with nothing unnecessary added to interject confusion.
Original NASA ASRS Text
Title: Air carrier Captain reported that the Controller Pilot Data Link Communication format interjects superfluous; ambiguous and contradictory information into the clearance that introduces confusion and uncertainty rather than clarifying the issue with a definitive; easily understood change.
Narrative: The most recent issue of NASA's ASRS newsletter was dedicated to this same issue of confusing Controller Pilot Data Link Communications (CPDLC) clearances given at the departing airport. Multiple times in the past month I have received a revised clearance. Every time; the format used by the FAA interjects superfluous; ambiguous and contradictory information into the clearance that introduces confusion and uncertainty rather than a definitive; easily understood change.CLEARED TO CNX VIAROUTE CLEARANCE VIA TODIRECT CRGERN3026.9 W9820.5+LOAD NEW ROUTE TO CNX+ AFTERCNX CLEARED TO ZZZ ARPT AS FILEDPITZZ4. CRGER.....We are not cleared to CNX; we are cleared to ZZZ; but you have to go 7 lines down to see that… It says 'DIRECT CRGER;' but indeed we are NOT cleared direct to CRGER; but via the PITZZ4 departure...Then there is a coordinate given. Is this an additional point? This does not match the coordinates for CRGER in either our NAV Database; nor our JeppFD-Pro. All of the additional information issued in via the CPDLC only confuses the issue. The first 8 lines of the routing info in on the clearance should be deleted. It would be clear; unambiguous and not contradictory to simply say:REVISED ROUTING:PITTZ4 CRGER AS FILEDNo confusion; no contradictions; no mismatched databases. Completely understandable with nothing unnecessary added to interject confusion.
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.