UNFAMILIARITY WITH A COMPUTER FILED FLT PLAN LEADS A PLT TO A TRACK DEV DEPARTING SNA; CA; WHEN THE FILED DEP WAS NOT FLOWN.

Date: 2002-09 · Aircraft: Beechjet 400 · Phase: initial_climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

UNFAMILIARITY WITH A COMPUTER FILED FLT PLAN LEADS A PLT TO A TRACK DEV DEPARTING SNA; CA; WHEN THE FILED DEP WAS NOT FLOWN.

Narrative

FILED IFR FLT PLAN USING COMMERCIAL COMPUTER PROGRAM VIA WTC COMPUTER PROVIDED BY FBO. I HAD NEVER USED THIS PROGRAM BEFORE AND WAS UNFAMILIAR. THE PIC FOR THE FLT WAS FAMILIAR WITH THE PROGRAM AND GUIDED ME THROUGH ITS USE. WHEN THE FLT PLAN WAS FILED; WE PRINTED THE PLAN. I PROGRAMMED THE FMS IN THE ACFT USING THE PRINTED FORMS AS A GUIDE. I DID NOT SEE A SPECIFIC DEP ASSIGNED AND ASSUMED THAT WE WOULD RECEIVE VECTORS TO OUR FIRST FIX. WHEN THE BEFORE TKOF BRIEF WAS PERFORMED BY ME (I WAS THE PF) I BRIEFED WE WOULD FOLLOW TWR'S INSTRUCTIONS FOR TKOF TO VECTORS OUT TO SXC. DURING THE TKOF ROLL; THE PNF INQUIRED AS TO WHICH DEP WE HAD BEEN ASSIGNED. WE WERE AT VR AND CONTINUED THE TKOF REALIZING THAT WE WERE CONFUSED AS TO WHAT SPECIFIC DEP WE SHOULD HAVE BEEN EXECUTING. THE CLRNC WE RECEIVED WAS 'AS FILED....' MY UNFAMILIARITY WITH THE COM PROGRAM RESULTED IN MY OVERLOOKING A SECTION OF THE 2-3 PAGE PRINTOUT WHICH REVEALED THE DEP PROC; WHICH WAS VECTORS TO SXC AFTER A HDG OTHER THAN RWY HDG PER NOISE ABATEMENT (I DO NOT RECALL THE NAME OF THE DEP). WHEN I REALIZED THERE WAS CONFUSION; I PERFORMED A NOISE ABATEMENT TKOF. TO MY KNOWLEDGE; NO NOISE SENSORS WERE ACTIVATED; NOR ANY OTHER TYPE OF CONFLICT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.