37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 112645 |
Time | |
Date | 198906 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : poc |
State Reference | CA |
Altitude | msl bound lower : 1400 msl bound upper : 1400 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : ont tower : poc |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | climbout : intermediate altitude cruise other |
Route In Use | enroute airway : ont |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 110 flight time total : 5400 flight time type : 30 |
ASRS Report | 112645 |
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 other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
When copying tower en route clearance from poc to vny, I used the same sheet of paper that was used earlier when I arrived IFR from vny. Therefore, when switching over to departure frequency, I set in the frequency of the facility I used in my previous flight. This took a minute or so to resolve (I went back to poc tower which advised of the correct frequency). During this period of confusion, I set in my next airway (I had just intercepted V363) which is V186. The airways comprised of pdz 112.2 but I set in the frequency of an adjacent t-vor (riverside 112.4) and intercepted what I believed to be the airway and turned on course. When I contacted ontario departure on the correct frequency, the controller was upset about the communication error and the path I was following (wrong VOR). Upon reflection, I believe it is important not to re-use paper that has old flight information as that is where the confusion started. Also, it is important to double-check VOR frequency information, especially in congested areas as los angeles, since it is very easy to enter information from nearby VOR's.
Original NASA ASRS Text
Title: PLT REUSED PAPER FROM APCH CLRNC TO COPY DEP CLRNC. CONSEQUENTLY SELECTED WRONG FREQ FOR DEP CTL. RETUNED TWR TO DETERMINE CORRECT FREQ WHILE SETTING UP VOR. TUNED WRONG VOR FREQ. FOLLOWED WRONG AIRWAY.
Narrative: WHEN COPYING TWR ENRTE CLRNC FROM POC TO VNY, I USED THE SAME SHEET OF PAPER THAT WAS USED EARLIER WHEN I ARRIVED IFR FROM VNY. THEREFORE, WHEN SWITCHING OVER TO DEP FREQ, I SET IN THE FREQ OF THE FAC I USED IN MY PREVIOUS FLT. THIS TOOK A MINUTE OR SO TO RESOLVE (I WENT BACK TO POC TWR WHICH ADVISED OF THE CORRECT FREQ). DURING THIS PERIOD OF CONFUSION, I SET IN MY NEXT AIRWAY (I HAD JUST INTERCEPTED V363) WHICH IS V186. THE AIRWAYS COMPRISED OF PDZ 112.2 BUT I SET IN THE FREQ OF AN ADJACENT T-VOR (RIVERSIDE 112.4) AND INTERCEPTED WHAT I BELIEVED TO BE THE AIRWAY AND TURNED ON COURSE. WHEN I CONTACTED ONTARIO DEP ON THE CORRECT FREQ, THE CTLR WAS UPSET ABOUT THE COM ERROR AND THE PATH I WAS FOLLOWING (WRONG VOR). UPON REFLECTION, I BELIEVE IT IS IMPORTANT NOT TO RE-USE PAPER THAT HAS OLD FLT INFO AS THAT IS WHERE THE CONFUSION STARTED. ALSO, IT IS IMPORTANT TO DOUBLE-CHECK VOR FREQ INFO, ESPECIALLY IN CONGESTED AREAS AS LOS ANGELES, SINCE IT IS VERY EASY TO ENTER INFO FROM NEARBY VOR'S.
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.