37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 342650 |
Time | |
Date | 199607 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : gso |
State Reference | NC |
Altitude | msl bound lower : 6000 msl bound upper : 6000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : gso |
Operator | general aviation : corporate |
Make Model Name | PA-31 Navajo Chieftan/Mojave/Navajo T1020 |
Operating Under FAR Part | Part 135 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 6200 flight time type : 100 |
ASRS Report | 342650 |
Person 2 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Pilot Deviation |
Narrative:
Controller issued clearance 'as filed.' we have canned flight plans and last one I was given by company was filed buy direct lzu. So that's what I was doing when gso departure control called back and asked if I was going to bzm. I responded going direct to lzu. Then he said my flight plan said buy-bzm-vzo- genod intersection-lzu. So then I did that and called my company at next stop and queried them. They said they had changed the flight plan and claimed to have posted a note about it, that possibly someone took note down to copy it and forgot to re-post it. I didn't get any indication from gso that there was any problem with traffic conflicts which is good, and I suggested to my company they need to put a note in every pilot's mailbox when they make changes that can compromise safety as well as each pilot's license.
Original NASA ASRS Text
Title: RPTR PLT COMPANY CHANGED CANNED FLT PLAN WITHOUT NOTIFYING THE RPTR. WHEN CALLING FOR CLRNC, HE WAS GIVEN 'AS FILED.' NOT KNOWING HIS COMPANY HAD CHANGED THE ROUTING, HE WENT OFF COURSE UNTIL ATC INTERVENED AND GAVE HIM THE CORRECT ROUTING.
Narrative: CTLR ISSUED CLRNC 'AS FILED.' WE HAVE CANNED FLT PLANS AND LAST ONE I WAS GIVEN BY COMPANY WAS FILED BUY DIRECT LZU. SO THAT'S WHAT I WAS DOING WHEN GSO DEP CTL CALLED BACK AND ASKED IF I WAS GOING TO BZM. I RESPONDED GOING DIRECT TO LZU. THEN HE SAID MY FLT PLAN SAID BUY-BZM-VZO- GENOD INTXN-LZU. SO THEN I DID THAT AND CALLED MY COMPANY AT NEXT STOP AND QUERIED THEM. THEY SAID THEY HAD CHANGED THE FLT PLAN AND CLAIMED TO HAVE POSTED A NOTE ABOUT IT, THAT POSSIBLY SOMEONE TOOK NOTE DOWN TO COPY IT AND FORGOT TO RE-POST IT. I DIDN'T GET ANY INDICATION FROM GSO THAT THERE WAS ANY PROB WITH TFC CONFLICTS WHICH IS GOOD, AND I SUGGESTED TO MY COMPANY THEY NEED TO PUT A NOTE IN EVERY PLT'S MAILBOX WHEN THEY MAKE CHANGES THAT CAN COMPROMISE SAFETY AS WELL AS EACH PLT'S LICENSE.
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.