37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 118956 |
Time | |
Date | 198908 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : mxe |
State Reference | PA |
Altitude | msl bound lower : 11000 msl bound upper : 11000 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Transport |
Flight Phase | cruise other |
Route In Use | enroute airway : v378 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 250 flight time total : 2550 flight time type : 420 |
ASRS Report | 118956 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were flying a scheduled segment from hpn to dca. Neither the captain nor myself had flown that particular segment in several weeks (possibly months), but had, in fact, flown hpn-bwi quite frequently. Subconsciously we both must have been thinking bwi, because I looked down at a standby radio and noticed the bwi ATIS tuned in. As I was about to bring this to the captain's attention, he himself noticed that and promptly switched to dca frequency (ATIS). At this point, I asked the captain to confirm our routing to oca after modena (VOR). His reply was that we were to proceed on V378 after modena VOR (note: original clearance received in hpn was 'as filed'). When we reached modena, we proceeded outbnd on V378. I felt as if that could be wrong, so I proceeded to look up the information. The first thing I pulled out was the dispatch release. Unfortunately, the previous day, our company was involved in a merger. Many changes took place in computer operations and paperwork and, to my dismay, our stored flight plans were no longer printed on the release for quick reference. I commented on how I felt the old system was superior in that it provided much visibility information. While proceeding to look further, ATC questioned us to verify that we were on V408 (nike 267 degree right), and the captain replied, 'our as filed is V378.' at that time I found our stored flight plan and the controller was correct--and the controller was somewhat annoyed (understandably so) because he mistook us for another aircraft that earlier requested and had been cleared V378. We convinced him that no, we hadn't requested that and that our misunderstanding was genuine. He gave us a vector to rejoin the proper arwy. I plotted our position and I estimate that we were still within the correct arwy's airspace. Also, to my knowledge, no conflict with another aircraft had arisen.
Original NASA ASRS Text
Title: FLT CREW OF MDT FLEW WRONG AIRWAY.
Narrative: WE WERE FLYING A SCHEDULED SEGMENT FROM HPN TO DCA. NEITHER THE CAPT NOR MYSELF HAD FLOWN THAT PARTICULAR SEGMENT IN SEVERAL WKS (POSSIBLY MONTHS), BUT HAD, IN FACT, FLOWN HPN-BWI QUITE FREQUENTLY. SUBCONSCIOUSLY WE BOTH MUST HAVE BEEN THINKING BWI, BECAUSE I LOOKED DOWN AT A STANDBY RADIO AND NOTICED THE BWI ATIS TUNED IN. AS I WAS ABOUT TO BRING THIS TO THE CAPT'S ATTN, HE HIMSELF NOTICED THAT AND PROMPTLY SWITCHED TO DCA FREQ (ATIS). AT THIS POINT, I ASKED THE CAPT TO CONFIRM OUR ROUTING TO OCA AFTER MODENA (VOR). HIS REPLY WAS THAT WE WERE TO PROCEED ON V378 AFTER MODENA VOR (NOTE: ORIGINAL CLRNC RECEIVED IN HPN WAS 'AS FILED'). WHEN WE REACHED MODENA, WE PROCEEDED OUTBND ON V378. I FELT AS IF THAT COULD BE WRONG, SO I PROCEEDED TO LOOK UP THE INFO. THE FIRST THING I PULLED OUT WAS THE DISPATCH RELEASE. UNFORTUNATELY, THE PREVIOUS DAY, OUR COMPANY WAS INVOLVED IN A MERGER. MANY CHANGES TOOK PLACE IN COMPUTER OPS AND PAPERWORK AND, TO MY DISMAY, OUR STORED FLT PLANS WERE NO LONGER PRINTED ON THE RELEASE FOR QUICK REF. I COMMENTED ON HOW I FELT THE OLD SYS WAS SUPERIOR IN THAT IT PROVIDED MUCH VIS INFO. WHILE PROCEEDING TO LOOK FURTHER, ATC QUESTIONED US TO VERIFY THAT WE WERE ON V408 (NIKE 267 DEG R), AND THE CAPT REPLIED, 'OUR AS FILED IS V378.' AT THAT TIME I FOUND OUR STORED FLT PLAN AND THE CTLR WAS CORRECT--AND THE CTLR WAS SOMEWHAT ANNOYED (UNDERSTANDABLY SO) BECAUSE HE MISTOOK US FOR ANOTHER ACFT THAT EARLIER REQUESTED AND HAD BEEN CLRED V378. WE CONVINCED HIM THAT NO, WE HADN'T REQUESTED THAT AND THAT OUR MISUNDERSTANDING WAS GENUINE. HE GAVE US A VECTOR TO REJOIN THE PROPER ARWY. I PLOTTED OUR POS AND I ESTIMATE THAT WE WERE STILL WITHIN THE CORRECT ARWY'S AIRSPACE. ALSO, TO MY KNOWLEDGE, NO CONFLICT WITH ANOTHER ACFT HAD ARISEN.
Data retrieved from NASA's ASRS site as of August 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.