 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Heading track deviation experienced by a B757 flight crew when they misinterped their clearance involving a WYLDD2 RNAV departure procedure, having filed a pgs transition, versus a clearance received for WYLDD2, tbc, flight plan route, at las, nv.
| Attributes | |
| ACN | 575598 |
| Time | |
| Date | 200303 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| State Reference | NV |
| Altitude | msl single value : 25000 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zla.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Route In Use | departure sid : wyldd2 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 100 flight time total : 14000 flight time type : 2000 |
| ASRS Report | 575598 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : returned to intended or assigned course |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | Company Flight Crew Human Performance Airspace Structure ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Filed routing was from las to jfk via WYLDD2 departure to pgs, J64 fmn, J44... First officer got clearance prior to departure and copied 'WYLDD2 departure, tbc, as filed.' WYLDD2 departure does not have a tbc transition, but J64 goes from pgs to tbc, so he assumed we were still to follow the pgs transition. Shortly after passing wyldd intersection, ZLA cleared us direct tbc and asked why we were going over pgs. They also had us call on phone from jfk. ZLA explained pgs is an arrival fix, and they don't want us using it on departure. No conflict occurred, and they assured me 'no paperwork' would be filed. Seems odd a SID would have a transition they don't want you to use. I also contacted company liaison for ATC to have company dispatchers not file over pgs when going eastbound out of las.
Original NASA ASRS Text
Title: HDG TRACK DEV EXPERIENCED BY A B757 FLT CREW WHEN THEY MISINTERPED THEIR CLRNC INVOLVING A WYLDD2 RNAV DEP PROC, HAVING FILED A PGS TRANSITION, VERSUS A CLRNC RECEIVED FOR WYLDD2, TBC, FLT PLAN RTE, AT LAS, NV.
Narrative: FILED ROUTING WAS FROM LAS TO JFK VIA WYLDD2 DEP TO PGS, J64 FMN, J44... FO GOT CLRNC PRIOR TO DEP AND COPIED 'WYLDD2 DEP, TBC, AS FILED.' WYLDD2 DEP DOES NOT HAVE A TBC TRANSITION, BUT J64 GOES FROM PGS TO TBC, SO HE ASSUMED WE WERE STILL TO FOLLOW THE PGS TRANSITION. SHORTLY AFTER PASSING WYLDD INTXN, ZLA CLRED US DIRECT TBC AND ASKED WHY WE WERE GOING OVER PGS. THEY ALSO HAD US CALL ON PHONE FROM JFK. ZLA EXPLAINED PGS IS AN ARR FIX, AND THEY DON'T WANT US USING IT ON DEP. NO CONFLICT OCCURRED, AND THEY ASSURED ME 'NO PAPERWORK' WOULD BE FILED. SEEMS ODD A SID WOULD HAVE A TRANSITION THEY DON'T WANT YOU TO USE. I ALSO CONTACTED COMPANY LIAISON FOR ATC TO HAVE COMPANY DISPATCHERS NOT FILE OVER PGS WHEN GOING EBOUND OUT OF LAS.
Data retrieved from NASA's ASRS site as of July 2007 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.