An small aircraft pilot experiences a heading track deviation while following a supposedly correct flight plan. It wasn't and he erred.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	410380
Time
Date	199808
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : buf
State Reference	NY
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : czyz
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : flight engineer pilot : cfi pilot : atp
Experience	flight time last 90 days : 175 flight time total : 23337 flight time type : 2136
ASRS Report	410380
Person 2
Affiliation	government other
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

On sunday, I filed a flight plan with green bay FSS. The route was: grb V55 mkg-V450-zr-V308-yxu-V84-thorl-V265-bfd. The FSS specialist could not get the computer to accept the flight plan until zr and thorl were deleted. The route then was: grb V55-mkg-V450-V308-yxu V84-V265 bfd. This flight was canceled due to a minor mechanical problem. On tuesday I filed another flight plan for bfd. Due to WX in michigan the route was: grb-V420-tvc-V133-mbs-V216-eck-V84-V265-bfd. The green bay FSS specialist said the computer accepted this route. I was given a cleared as filed by green bay clearance. After departure, ZMP asked what my destination was. I was working toronto center as I approached thorl intersection (the junction of V84 and V265). When I turned to intercept V265, toronto asked if I was deviating around WX. It became obvious that there was a problem with the routing. I received clearance for V265 and was changed to buffalo approach. I asked them about the flight plan. They said that they and toronto had problems with the flight plan. Apparently the route information was not transmitted properly.

Original NASA ASRS Text

Title: AN SMA PLT EXPERIENCES A HDG TRACK DEV WHILE FOLLOWING A SUPPOSEDLY CORRECT FLT PLAN. IT WASN'T AND HE ERRED.

Narrative: ON SUNDAY, I FILED A FLT PLAN WITH GREEN BAY FSS. THE RTE WAS: GRB V55 MKG-V450-ZR-V308-YXU-V84-THORL-V265-BFD. THE FSS SPECIALIST COULD NOT GET THE COMPUTER TO ACCEPT THE FLT PLAN UNTIL ZR AND THORL WERE DELETED. THE RTE THEN WAS: GRB V55-MKG-V450-V308-YXU V84-V265 BFD. THIS FLT WAS CANCELED DUE TO A MINOR MECHANICAL PROB. ON TUESDAY I FILED ANOTHER FLT PLAN FOR BFD. DUE TO WX IN MICHIGAN THE RTE WAS: GRB-V420-TVC-V133-MBS-V216-ECK-V84-V265-BFD. THE GREEN BAY FSS SPECIALIST SAID THE COMPUTER ACCEPTED THIS RTE. I WAS GIVEN A CLRED AS FILED BY GREEN BAY CLRNC. AFTER DEP, ZMP ASKED WHAT MY DEST WAS. I WAS WORKING TORONTO CTR AS I APCHED THORL INTXN (THE JUNCTION OF V84 AND V265). WHEN I TURNED TO INTERCEPT V265, TORONTO ASKED IF I WAS DEVIATING AROUND WX. IT BECAME OBVIOUS THAT THERE WAS A PROB WITH THE ROUTING. I RECEIVED CLRNC FOR V265 AND WAS CHANGED TO BUFFALO APCH. I ASKED THEM ABOUT THE FLT PLAN. THEY SAID THAT THEY AND TORONTO HAD PROBS WITH THE FLT PLAN. APPARENTLY THE RTE INFO WAS NOT XMITTED PROPERLY.

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.