37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 559456 |
Time | |
Date | 200209 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sna.airport |
State Reference | CA |
Altitude | agl single value : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | general aviation : corporate |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | climbout : initial |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : cfi pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 3000 flight time type : 200 |
ASRS Report | 559456 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : became reoriented |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Filed IFR flight 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 flight was familiar with the program and guided me through its use. When the flight plan was filed, we printed the plan. I programmed the FMS in the aircraft using the printed forms as a guide. I did not see a specific departure assigned and assumed that we would receive vectors to our first fix. When the before takeoff brief was performed by me (I was the PF) I briefed we would follow tower's instructions for takeoff to vectors out to sxc. During the takeoff roll, the PNF inquired as to which departure we had been assigned. We were at vr and continued the takeoff realizing that we were confused as to what specific departure we should have been executing. The clearance we received was 'as filed....' my unfamiliarity with the communication program resulted in my overlooking a section of the 2-3 page printout which revealed the departure procedure, which was vectors to sxc after a heading other than runway heading per noise abatement (I do not recall the name of the departure). When I realized there was confusion, I performed a noise abatement takeoff. To my knowledge, no noise sensors were activated, nor any other type of conflict.
Original NASA ASRS Text
Title: 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.
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.