37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 304079 |
Time | |
Date | 199505 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : con |
State Reference | NH |
Altitude | msl bound lower : 16000 msl bound upper : 16000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zbw |
Operator | common carrier : air carrier |
Make Model Name | Dash 8 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute airway : zbw |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : instrument pilot : private |
Experience | flight time last 90 days : 185 flight time total : 16852 flight time type : 3494 |
ASRS Report | 304079 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 32 flight time total : 3700 flight time type : 1100 |
ASRS Report | 303877 |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was doing roe (requalifying operations experience) with a first officer recalled from furlough. We had just completed the originating cockpit checklist and the first officer was starting to fill out the necessary paperwork needed prior to leaving the gate. It was an early morning departure and the first time the first officer had originated a flight in several months. To help ease his work load, I called for and received the ATC clearance from clearance delivery. They gave us a full route clearance, but it was the same route we had been using for yrs. When the gate agent brought the dispatch release to the flight deck, I checked all of the information, but failed to insure the route on the release was in fact the same as the clearance. The first officer programmed the FMS and compared the route on the release with the flight plan stored in the FMS which were exact. However, when the departure crew briefing was given, I read back the clearance I copied from clearance delivery but did not compare it with the FMS route (mistake #1). The first fix on the FMS and on the clearance were the same, but the route changed after that. A few mi after the first fix, ZBW asked what route we were issued. I had the release in my hand at that particular moment, so I read the filed route printed on it (mistake #2). ATC made no further comments about our route and issued a frequency change. Upon initial contact with the new controller, I asked him for a route verification and he said he was seated next to the controller we had communicated with on the previous frequency and our flight was cleared via the route I read back to him. Several lessons learned that day...1) have the FMS on line before the clearance is received so it may be compared with the stored filed flight plan immediately. 2) maintain a higher level of situational awareness. Supplemental information from acn 303877: I feel that because I was returning to line flying after a 4 month break I did not have the situational awareness to catch the error.
Original NASA ASRS Text
Title: A DHC-8 COMMUTER FLC CONFUSED THE DISPATCH RELEASE RTE WITH THE ATC CLRNC RTE. IN ERROR, THE DISPATCHED ROUTE WAS ENTERED INTO THE FMS (WITHOUT CLRNC XCHK) AND FOLLOWED BY THE CREW. CTLR INTERVENED.
Narrative: I WAS DOING ROE (REQUALIFYING OPS EXPERIENCE) WITH A FO RECALLED FROM FURLOUGH. WE HAD JUST COMPLETED THE ORIGINATING COCKPIT CHKLIST AND THE FO WAS STARTING TO FILL OUT THE NECESSARY PAPERWORK NEEDED PRIOR TO LEAVING THE GATE. IT WAS AN EARLY MORNING DEP AND THE FIRST TIME THE FO HAD ORIGINATED A FLT IN SEVERAL MONTHS. TO HELP EASE HIS WORK LOAD, I CALLED FOR AND RECEIVED THE ATC CLRNC FROM CLRNC DELIVERY. THEY GAVE US A FULL RTE CLRNC, BUT IT WAS THE SAME RTE WE HAD BEEN USING FOR YRS. WHEN THE GATE AGENT BROUGHT THE DISPATCH RELEASE TO THE FLT DECK, I CHKED ALL OF THE INFO, BUT FAILED TO INSURE THE RTE ON THE RELEASE WAS IN FACT THE SAME AS THE CLRNC. THE FO PROGRAMMED THE FMS AND COMPARED THE RTE ON THE RELEASE WITH THE FLT PLAN STORED IN THE FMS WHICH WERE EXACT. HOWEVER, WHEN THE DEP CREW BRIEFING WAS GIVEN, I READ BACK THE CLRNC I COPIED FROM CLRNC DELIVERY BUT DID NOT COMPARE IT WITH THE FMS RTE (MISTAKE #1). THE FIRST FIX ON THE FMS AND ON THE CLRNC WERE THE SAME, BUT THE RTE CHANGED AFTER THAT. A FEW MI AFTER THE FIRST FIX, ZBW ASKED WHAT RTE WE WERE ISSUED. I HAD THE RELEASE IN MY HAND AT THAT PARTICULAR MOMENT, SO I READ THE FILED RTE PRINTED ON IT (MISTAKE #2). ATC MADE NO FURTHER COMMENTS ABOUT OUR RTE AND ISSUED A FREQ CHANGE. UPON INITIAL CONTACT WITH THE NEW CTLR, I ASKED HIM FOR A RTE VERIFICATION AND HE SAID HE WAS SEATED NEXT TO THE CTLR WE HAD COMMUNICATED WITH ON THE PREVIOUS FREQ AND OUR FLT WAS CLRED VIA THE RTE I READ BACK TO HIM. SEVERAL LESSONS LEARNED THAT DAY...1) HAVE THE FMS ON LINE BEFORE THE CLRNC IS RECEIVED SO IT MAY BE COMPARED WITH THE STORED FILED FLT PLAN IMMEDIATELY. 2) MAINTAIN A HIGHER LEVEL OF SITUATIONAL AWARENESS. SUPPLEMENTAL INFO FROM ACN 303877: I FEEL THAT BECAUSE I WAS RETURNING TO LINE FLYING AFTER A 4 MONTH BREAK I DID NOT HAVE THE SITUATIONAL AWARENESS TO CATCH THE ERROR.
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.