|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||airport : ase|
|Altitude||msl bound lower : 14000|
msl bound upper : 15
|Controlling Facilities||artcc : zdv|
tower : dbq
|Operator||general aviation : corporate|
|Make Model Name||Light Transport, Low Wing, 2 Turboprop Eng|
|Flight Phase||climbout : intermediate altitude|
|Route In Use||departure other|
enroute : direct
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
pilot : cfi
|Experience||flight time last 90 days : 90|
flight time total : 9500
flight time type : 2400
|Function||flight crew : first officer|
|Qualification||pilot : instrument|
pilot : commercial
|Anomaly||non adherence : clearance|
other spatial deviation
|Independent Detector||other controllera|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
While taxiing for takeoff my copilot and I were discussing our routing after takeoff. He had filed the inbound and outbnd legs with our computer service prior to departure from home base. They forward our flight plan request to FSS, then confirm their filings and we have the computer print out copies. My copilot confirmed to me that he had filed direct to sny as our first fix. I thought it odd, but did not question it because that is a more direct route of flight. Normally you depart over dbl. We took off in legal, but marginal VFR WX and avoided rain showers and a preceding commuter flight. Out of about 15000' we made contact with ZDV. He rogered our contact and asked to confirm we were going direct dbl. We said negative, that we were cleared as filed which we thought was direct sny. He replied that he showed dbl as our first point. I was not convinced we were on the right course and asked to see our computer printout. Sure enough, our first fix was dbl. The copilot swore he typed in the identify for sny, but in fact did put dbl first. I should have double checked my route request. I also should have backed up his statement by checking the printout. I don't think there was a conflict, but I would rather fly the route I requested and not one my copilot thinks he filed. Especially in a minimal radar environment. In the future I'll check my cohort's work more closely instead of just taking his word.
Original NASA ASRS Text
Title: CORP LTT TRACK DEVIATION.
Narrative: WHILE TAXIING FOR TKOF MY COPLT AND I WERE DISCUSSING OUR ROUTING AFTER TKOF. HE HAD FILED THE INBND AND OUTBND LEGS WITH OUR COMPUTER SVC PRIOR TO DEP FROM HOME BASE. THEY FORWARD OUR FLT PLAN REQUEST TO FSS, THEN CONFIRM THEIR FILINGS AND WE HAVE THE COMPUTER PRINT OUT COPIES. MY COPLT CONFIRMED TO ME THAT HE HAD FILED DIRECT TO SNY AS OUR FIRST FIX. I THOUGHT IT ODD, BUT DID NOT QUESTION IT BECAUSE THAT IS A MORE DIRECT ROUTE OF FLT. NORMALLY YOU DEPART OVER DBL. WE TOOK OFF IN LEGAL, BUT MARGINAL VFR WX AND AVOIDED RAIN SHOWERS AND A PRECEDING COMMUTER FLT. OUT OF ABOUT 15000' WE MADE CONTACT WITH ZDV. HE ROGERED OUR CONTACT AND ASKED TO CONFIRM WE WERE GOING DIRECT DBL. WE SAID NEGATIVE, THAT WE WERE CLRED AS FILED WHICH WE THOUGHT WAS DIRECT SNY. HE REPLIED THAT HE SHOWED DBL AS OUR FIRST POINT. I WAS NOT CONVINCED WE WERE ON THE RIGHT COURSE AND ASKED TO SEE OUR COMPUTER PRINTOUT. SURE ENOUGH, OUR FIRST FIX WAS DBL. THE COPLT SWORE HE TYPED IN THE IDENT FOR SNY, BUT IN FACT DID PUT DBL FIRST. I SHOULD HAVE DOUBLE CHKED MY ROUTE REQUEST. I ALSO SHOULD HAVE BACKED UP HIS STATEMENT BY CHKING THE PRINTOUT. I DON'T THINK THERE WAS A CONFLICT, BUT I WOULD RATHER FLY THE ROUTE I REQUESTED AND NOT ONE MY COPLT THINKS HE FILED. ESPECIALLY IN A MINIMAL RADAR ENVIRONMENT. IN THE FUTURE I'LL CHK MY COHORT'S WORK MORE CLOSELY INSTEAD OF JUST TAKING HIS WORD.
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.