|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Locale Reference||atc facility : zzzz.artcc|
|Operator||common carrier : charter|
|Make Model Name||Challenger Jet Undifferentiated or Other Model|
|Operating Under FAR Part||Part 135|
|Navigation In Use||ils localizer only : xx|
|Flight Phase||descent : intermediate altitude|
descent : approach
|Affiliation||company : charter|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||non adherence : far|
non adherence : company policies
|Independent Detector||other flight crewa|
|Resolutory Action||controller : issued new clearance|
none taken : anomaly accepted
|Problem Areas||Flight Crew Human Performance|
|Primary Problem||Flight Crew Human Performance|
Flight was a position flight from ZZZZ2 to ZZZZ; first officer. I believe originally the flight was scheduled from ZZZZ2 to ZZZZ1. Both I and my first officer received that information via dispatch on our blackberry's; we believe. This information we received several days in advance and it stuck in our heads. The actual flight plan we received was ZZZZ2 to ZZZZ. The correct destination. This information was input to the FMS and not noticed by either of the flight crew members initially. I removed the approach charts for ZZZZ1 and assumed those were the correct charts. The mistake was realized when I received the ATIS information for ZZZZ1 advertising ILS xx and I attempted to set the FMS for the ILS xx at ZZZZ1 only to discover there was no ILS in the database for ILS xx ZZZZ1; only an ILS xy. After several moments of confusion; I realized where the error was and instructed the first officer to obtain the correct airport charts for ZZZZ. After a thorough search by both crew members; we could not find any charts for ZZZZ on board the aircraft. We notified ATC of our predicament and they said they would be able to accommodate us. The approach required to land at ZZZZ was a radar/no-gyro type approach; which commenced uneventfully. ATC had no further concerns after we landed and we taxied in to end the flight. I believe the event occurred due to both crew members receiving old information on their blackberry's and not being notified of an update in the arrival airport combined with not checking the trip sheet the day of the flight. When I queried dispatch if the airport had changed; they could find no information indicating our original destination was ZZZZ1. Had we caught the error on the ground in ZZZZ2; there would have been no event; or had the charts been on board; there would have been no event. Or; if indeed dispatch made an error and failed to notify us of a change; the incident also would have been caught earlier or not occurred. Suggestion: we should probably make sure ZZZZ airport is normally in the europe approach chart books and normally updated since we are using this airport.
Original NASA ASRS Text
Title: FLT CREW IS DISPATCHED TO ARPT FOR WHICH THEY DON'T HAVE APPROACH CHARTS. THIS FACT IS DISCOVERED DURING DESCENT. ATC IS ACCOMMODATING.
Narrative: FLT WAS A POS FLT FROM ZZZZ2 TO ZZZZ; FO. I BELIEVE ORIGINALLY THE FLT WAS SCHEDULED FROM ZZZZ2 TO ZZZZ1. BOTH I AND MY FO RECEIVED THAT INFO VIA DISPATCH ON OUR BLACKBERRY'S; WE BELIEVE. THIS INFO WE RECEIVED SEVERAL DAYS IN ADVANCE AND IT STUCK IN OUR HEADS. THE ACTUAL FLT PLAN WE RECEIVED WAS ZZZZ2 TO ZZZZ. THE CORRECT DEST. THIS INFO WAS INPUT TO THE FMS AND NOT NOTICED BY EITHER OF THE FLT CREW MEMBERS INITIALLY. I REMOVED THE APCH CHARTS FOR ZZZZ1 AND ASSUMED THOSE WERE THE CORRECT CHARTS. THE MISTAKE WAS REALIZED WHEN I RECEIVED THE ATIS INFO FOR ZZZZ1 ADVERTISING ILS XX AND I ATTEMPTED TO SET THE FMS FOR THE ILS XX AT ZZZZ1 ONLY TO DISCOVER THERE WAS NO ILS IN THE DATABASE FOR ILS XX ZZZZ1; ONLY AN ILS XY. AFTER SEVERAL MOMENTS OF CONFUSION; I REALIZED WHERE THE ERROR WAS AND INSTRUCTED THE FO TO OBTAIN THE CORRECT ARPT CHARTS FOR ZZZZ. AFTER A THOROUGH SEARCH BY BOTH CREW MEMBERS; WE COULD NOT FIND ANY CHARTS FOR ZZZZ ON BOARD THE ACFT. WE NOTIFIED ATC OF OUR PREDICAMENT AND THEY SAID THEY WOULD BE ABLE TO ACCOMMODATE US. THE APCH REQUIRED TO LAND AT ZZZZ WAS A RADAR/NO-GYRO TYPE APCH; WHICH COMMENCED UNEVENTFULLY. ATC HAD NO FURTHER CONCERNS AFTER WE LANDED AND WE TAXIED IN TO END THE FLT. I BELIEVE THE EVENT OCCURRED DUE TO BOTH CREW MEMBERS RECEIVING OLD INFO ON THEIR BLACKBERRY'S AND NOT BEING NOTIFIED OF AN UPDATE IN THE ARR ARPT COMBINED WITH NOT CHKING THE TRIP SHEET THE DAY OF THE FLT. WHEN I QUERIED DISPATCH IF THE ARPT HAD CHANGED; THEY COULD FIND NO INFO INDICATING OUR ORIGINAL DEST WAS ZZZZ1. HAD WE CAUGHT THE ERROR ON THE GND IN ZZZZ2; THERE WOULD HAVE BEEN NO EVENT; OR HAD THE CHARTS BEEN ON BOARD; THERE WOULD HAVE BEEN NO EVENT. OR; IF INDEED DISPATCH MADE AN ERROR AND FAILED TO NOTIFY US OF A CHANGE; THE INCIDENT ALSO WOULD HAVE BEEN CAUGHT EARLIER OR NOT OCCURRED. SUGGESTION: WE SHOULD PROBABLY MAKE SURE ZZZZ ARPT IS NORMALLY IN THE EUROPE APCH CHART BOOKS AND NORMALLY UPDATED SINCE WE ARE USING THIS ARPT.
Data retrieved from NASA's ASRS site as of May 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.