37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 421912 |
Time | |
Date | 199812 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : cyn |
State Reference | NJ |
Altitude | msl bound lower : 29000 msl bound upper : 29000 |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Route In Use | enroute : on vectors enroute airway : zny |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer |
Experience | flight time last 90 days : 40 flight time total : 11000 flight time type : 7000 |
ASRS Report | 421912 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : commercial |
Events | |
Anomaly | non adherence : far non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Pilot Deviation |
Narrative:
Trip was planned as a crp passenger drop-off/quick turn in phl continuing to swf. While I was assisting the passenger to their transportation, the co-captain received ATC clearance via pre departure clearance. I had verbally filed a flight plan with FSS with a routing we had previously flown and stored in the FMS: ditch, V312, cyn, jfk, dpk, mad, MAD341, briss, phl, V433, tresa, swf. The co-captain loaded that flight plan into both FMS's. The pre departure clearance was the same routing as filed except for the initial airway. When I returned to the cockpit I reviewed the pre departure clearance on the FMS and was surprised to see 'as filed' since the routing almost always changes. We both missed the change to the initial portion of the clearance: ditch J225 jfk as filed. After takeoff, we were given vectors in the general direction of ditch, then cleared direct. After passing ditch, still climbing to FL290 we were proceeding to cyn when the controller gave us a heading of 010 degrees to intercept J225. As we were not prepared for the fix/radial of that airway, we looked at the united states high chart and had a great deal of trouble locating the airway. In that area, J225 begins at vcn, and the identify for that airway on the chart was far south of our present location. By the time we located the airway and were tuning the radios, we were probably through the route. The controller (ZNY) asked us 'if we even knew where J225 was' and told us to proceed direct to dpk. I believe that we missed the J225 readout on the pre departure clearance due to the way it was presented on the FMS. Ditch was there as was jfk and as filed, however, the sentence break on the FMS was such that J225 was missed. If we had received the clearance via radio it would have been written down and the FMS reprogrammed for the correct routing to jfk. Contributing to this was my absence from the cockpit while the FMS was programmed and reliance on the as filed statement in the clearance. While we do not think we violated any regulation, improper programming of FMS/EFIS equipped aircraft seems to be a recurring problem area, as brought out in several ASRS reports. We have reviewed our clearance delivery procedures as they apply to the afis pre departure clearance system as well as our FMS programming. One pilot will load and compare the flight plan with the one received via afis, the other will load the flight plan received by clearance delivery (or pre departure clearance). The flight plan from pre departure clearance will be displayed via the 'clearance' readout on the FMS and both will be compared on the multi-function display. In this manner, reliance on our stored 'pilot rtes' that differ from our clearance will be readily idented.
Original NASA ASRS Text
Title: FLC OF A CPR B727 FAILED TO FOLLOW ASSIGNED TRACK DURING CLB DUE TO NOT REPROGRAMMING THE FMS WITH THE ACTUAL CLRNC GIVEN IN THEIR PDC.
Narrative: TRIP WAS PLANNED AS A CRP PAX DROP-OFF/QUICK TURN IN PHL CONTINUING TO SWF. WHILE I WAS ASSISTING THE PAX TO THEIR TRANSPORTATION, THE CO-CAPT RECEIVED ATC CLRNC VIA PDC. I HAD VERBALLY FILED A FLT PLAN WITH FSS WITH A ROUTING WE HAD PREVIOUSLY FLOWN AND STORED IN THE FMS: DITCH, V312, CYN, JFK, DPK, MAD, MAD341, BRISS, PHL, V433, TRESA, SWF. THE CO-CAPT LOADED THAT FLT PLAN INTO BOTH FMS'S. THE PDC WAS THE SAME ROUTING AS FILED EXCEPT FOR THE INITIAL AIRWAY. WHEN I RETURNED TO THE COCKPIT I REVIEWED THE PDC ON THE FMS AND WAS SURPRISED TO SEE 'AS FILED' SINCE THE ROUTING ALMOST ALWAYS CHANGES. WE BOTH MISSED THE CHANGE TO THE INITIAL PORTION OF THE CLRNC: DITCH J225 JFK AS FILED. AFTER TKOF, WE WERE GIVEN VECTORS IN THE GENERAL DIRECTION OF DITCH, THEN CLRED DIRECT. AFTER PASSING DITCH, STILL CLBING TO FL290 WE WERE PROCEEDING TO CYN WHEN THE CTLR GAVE US A HDG OF 010 DEGS TO INTERCEPT J225. AS WE WERE NOT PREPARED FOR THE FIX/RADIAL OF THAT AIRWAY, WE LOOKED AT THE UNITED STATES HIGH CHART AND HAD A GREAT DEAL OF TROUBLE LOCATING THE AIRWAY. IN THAT AREA, J225 BEGINS AT VCN, AND THE IDENT FOR THAT AIRWAY ON THE CHART WAS FAR S OF OUR PRESENT LOCATION. BY THE TIME WE LOCATED THE AIRWAY AND WERE TUNING THE RADIOS, WE WERE PROBABLY THROUGH THE RTE. THE CTLR (ZNY) ASKED US 'IF WE EVEN KNEW WHERE J225 WAS' AND TOLD US TO PROCEED DIRECT TO DPK. I BELIEVE THAT WE MISSED THE J225 READOUT ON THE PDC DUE TO THE WAY IT WAS PRESENTED ON THE FMS. DITCH WAS THERE AS WAS JFK AND AS FILED, HOWEVER, THE SENTENCE BREAK ON THE FMS WAS SUCH THAT J225 WAS MISSED. IF WE HAD RECEIVED THE CLRNC VIA RADIO IT WOULD HAVE BEEN WRITTEN DOWN AND THE FMS REPROGRAMMED FOR THE CORRECT ROUTING TO JFK. CONTRIBUTING TO THIS WAS MY ABSENCE FROM THE COCKPIT WHILE THE FMS WAS PROGRAMMED AND RELIANCE ON THE AS FILED STATEMENT IN THE CLRNC. WHILE WE DO NOT THINK WE VIOLATED ANY REG, IMPROPER PROGRAMMING OF FMS/EFIS EQUIPPED ACFT SEEMS TO BE A RECURRING PROB AREA, AS BROUGHT OUT IN SEVERAL ASRS RPTS. WE HAVE REVIEWED OUR CLRNC DELIVERY PROCS AS THEY APPLY TO THE AFIS PDC SYS AS WELL AS OUR FMS PROGRAMMING. ONE PLT WILL LOAD AND COMPARE THE FLT PLAN WITH THE ONE RECEIVED VIA AFIS, THE OTHER WILL LOAD THE FLT PLAN RECEIVED BY CLRNC DELIVERY (OR PDC). THE FLT PLAN FROM PDC WILL BE DISPLAYED VIA THE 'CLRNC' READOUT ON THE FMS AND BOTH WILL BE COMPARED ON THE MULTI-FUNCTION DISPLAY. IN THIS MANNER, RELIANCE ON OUR STORED 'PLT RTES' THAT DIFFER FROM OUR CLRNC WILL BE READILY IDENTED.
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.