|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||airport : bos.airport|
|Altitude||msl single value : 3000|
|Operator||common carrier : air carrier|
|Make Model Name||A319|
|Operating Under FAR Part||Part 121|
|Navigation In Use||other|
|Flight Phase||climbout : initial|
|Route In Use||departure sid : wylyy|
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Experience||flight time last 90 days : 250|
flight time total : 7000
flight time type : 1600
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Anomaly||non adherence : clearance|
non adherence : published procedure
non adherence other
|Independent Detector||other flight crewa|
|Resolutory Action||controller : issued new clearance|
|Consequence||faa : reviewed incident with flight crew|
|Problem Areas||Chart Or Publication|
Flight Crew Human Performance
|Primary Problem||Flight Crew Human Performance|
Received pre departure clearance about 15 mins prior to push. Noted revisions to pre departure clearance for routing after glyde; but never caught change to routing on wylyy FMS departure that specified bosox transition. Workload was average at the time. I did not load FMGC; but did verify and insert revision to route. Since wylyy FMS does terminate with radar vectors to follow on route fix; I did not suspect error with routing until we were airborne. During takeoff phase; level at 3000 ft and proceeding toward wylyy overfly fix; I had the captain query controller as to what to expect after wylyy intersection. We were given a heading of 235 degrees (which is heading toward cyoti). Departure controller then queried us as to what we were expecting and we responded that we thought we would receive follow-on vectors after wylyy to glyde. After a very brief discussion; we were able to determine that we had failed to load the bosox transition in for the wylyy which is why our FMGC showed a route discontinuity after wylyy versus bosox. The bosox transition was specified in the pre departure clearance; but not on the flight plan and we had missed it. Not many clues on the wylyy FMS departure page to indicate the expected transitions for various departure corridors which might help. The controller did not indicate there was any serious problem with our error since we had clarified a follow-on routing prior to reaching wylyy and there was no conflicting traffic. But we had inserted the departure incorrectly into the FMGC and it could have been a real problem. Re-emphasize checking the pre departure clearance carefully for revisions and transition routing (having a transition to a SID specified in the pre departure clearance and not on the flight plan is not a normal procedure). Every 'discontinuity' in routing in the FMGC should be clarified prior to arrival at the discontinuity. The wylyy RNAV departure could use some clarifying language concerning transition routings.
Original NASA ASRS Text
Title: AN A319 PLT COMMENTS ABOUT BOS WYLYY RNAV 5 SID INFO CLARITY AND EMPHASIZES CHKING PDC'S CAREFULLY TO ENSURE COMPLIANCE.
Narrative: RECEIVED PDC ABOUT 15 MINS PRIOR TO PUSH. NOTED REVISIONS TO PDC FOR ROUTING AFTER GLYDE; BUT NEVER CAUGHT CHANGE TO ROUTING ON WYLYY FMS DEP THAT SPECIFIED BOSOX TRANSITION. WORKLOAD WAS AVERAGE AT THE TIME. I DID NOT LOAD FMGC; BUT DID VERIFY AND INSERT REVISION TO RTE. SINCE WYLYY FMS DOES TERMINATE WITH RADAR VECTORS TO FOLLOW ON RTE FIX; I DID NOT SUSPECT ERROR WITH ROUTING UNTIL WE WERE AIRBORNE. DURING TKOF PHASE; LEVEL AT 3000 FT AND PROCEEDING TOWARD WYLYY OVERFLY FIX; I HAD THE CAPT QUERY CTLR AS TO WHAT TO EXPECT AFTER WYLYY INTXN. WE WERE GIVEN A HDG OF 235 DEGS (WHICH IS HEADING TOWARD CYOTI). DEP CTLR THEN QUERIED US AS TO WHAT WE WERE EXPECTING AND WE RESPONDED THAT WE THOUGHT WE WOULD RECEIVE FOLLOW-ON VECTORS AFTER WYLYY TO GLYDE. AFTER A VERY BRIEF DISCUSSION; WE WERE ABLE TO DETERMINE THAT WE HAD FAILED TO LOAD THE BOSOX TRANSITION IN FOR THE WYLYY WHICH IS WHY OUR FMGC SHOWED A RTE DISCONTINUITY AFTER WYLYY VERSUS BOSOX. THE BOSOX TRANSITION WAS SPECIFIED IN THE PDC; BUT NOT ON THE FLT PLAN AND WE HAD MISSED IT. NOT MANY CLUES ON THE WYLYY FMS DEP PAGE TO INDICATE THE EXPECTED TRANSITIONS FOR VARIOUS DEP CORRIDORS WHICH MIGHT HELP. THE CTLR DID NOT INDICATE THERE WAS ANY SERIOUS PROB WITH OUR ERROR SINCE WE HAD CLARIFIED A FOLLOW-ON ROUTING PRIOR TO REACHING WYLYY AND THERE WAS NO CONFLICTING TFC. BUT WE HAD INSERTED THE DEP INCORRECTLY INTO THE FMGC AND IT COULD HAVE BEEN A REAL PROB. RE-EMPHASIZE CHKING THE PDC CAREFULLY FOR REVISIONS AND TRANSITION ROUTING (HAVING A TRANSITION TO A SID SPECIFIED IN THE PDC AND NOT ON THE FLT PLAN IS NOT A NORMAL PROC). EVERY 'DISCONTINUITY' IN ROUTING IN THE FMGC SHOULD BE CLARIFIED PRIOR TO ARR AT THE DISCONTINUITY. THE WYLYY RNAV DEP COULD USE SOME CLARIFYING LANGUAGE CONCERNING TRANSITION ROUTINGS.
Data retrieved from NASA's ASRS site as of January 2009 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.