Narrative:

The problem arose due to out of date charts. The pilot crew had no reason to suspect that the company issued flight kit was out of date. The company had declared this flight kit was brand new. We received the 'new' flight kit on nov/fri/89 for a new upstart flight operation out of erie, PA beginning on nov/mon/89. Our normal run is from erie, PA to cleveland, oh. On nov/thu/89 our flight was dispatched to detroit, mi. On a pop-up unscheduled run which led to our discovery that our charts for the area were out of date. We suspected out of date chart when unable to find spica intersection (a clearance routing received from erie departure) on our low en route chart (#22). The actual discovery was made when given a heading to intercept airway, which we already indicated we were on. ATC then made mention that our chart was out of date. Corrective actions included picking up sufficient, up to date chart coverage before leaving detroit, mi and immediately notifying company to this issue. The kit was obviously not brand new. Revisions number 28 and 29 were missing. The crew has no way of knowing this and it is not considered frugal to question your company's integrity to this. A possible solution to deter the recurrence of such a problem would be for chart publisher to stamp the 'record of revision sheet' with the next revision due date or put the date by the last revision stamped since all pilots know that revisions come out every 2 weeks.

Google
 

Original NASA ASRS Text

Title: COMMUTER SMT FLEW FOR A WEEK WITH OUTDATED ROUTE CHARTS. ARTCC RADAR CTLR FINALLY DETECTED THE PROBLEM WHEN ACFT REPORTED ON TRACK BUT WAS NOT.

Narrative: THE PROBLEM AROSE DUE TO OUT OF DATE CHARTS. THE PLT CREW HAD NO REASON TO SUSPECT THAT THE COMPANY ISSUED FLT KIT WAS OUT OF DATE. THE COMPANY HAD DECLARED THIS FLT KIT WAS BRAND NEW. WE RECEIVED THE 'NEW' FLT KIT ON NOV/FRI/89 FOR A NEW UPSTART FLT OPERATION OUT OF ERIE, PA BEGINNING ON NOV/MON/89. OUR NORMAL RUN IS FROM ERIE, PA TO CLEVELAND, OH. ON NOV/THU/89 OUR FLT WAS DISPATCHED TO DETROIT, MI. ON A POP-UP UNSCHEDULED RUN WHICH LED TO OUR DISCOVERY THAT OUR CHARTS FOR THE AREA WERE OUT OF DATE. WE SUSPECTED OUT OF DATE CHART WHEN UNABLE TO FIND SPICA INTXN (A CLRNC ROUTING RECEIVED FROM ERIE DEP) ON OUR LOW ENRTE CHART (#22). THE ACTUAL DISCOVERY WAS MADE WHEN GIVEN A HDG TO INTERCEPT AIRWAY, WHICH WE ALREADY INDICATED WE WERE ON. ATC THEN MADE MENTION THAT OUR CHART WAS OUT OF DATE. CORRECTIVE ACTIONS INCLUDED PICKING UP SUFFICIENT, UP TO DATE CHART COVERAGE BEFORE LEAVING DETROIT, MI AND IMMEDIATELY NOTIFYING COMPANY TO THIS ISSUE. THE KIT WAS OBVIOUSLY NOT BRAND NEW. REVISIONS NUMBER 28 AND 29 WERE MISSING. THE CREW HAS NO WAY OF KNOWING THIS AND IT IS NOT CONSIDERED FRUGAL TO QUESTION YOUR COMPANY'S INTEGRITY TO THIS. A POSSIBLE SOLUTION TO DETER THE RECURRENCE OF SUCH A PROBLEM WOULD BE FOR CHART PUBLISHER TO STAMP THE 'RECORD OF REVISION SHEET' WITH THE NEXT REVISION DUE DATE OR PUT THE DATE BY THE LAST REVISION STAMPED SINCE ALL PLTS KNOW THAT REVISIONS COME OUT EVERY 2 WEEKS.

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.