 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of a beech BE58, turned the wrong way when vectored by alb approach controller due to tuning in the wrong VOR frequency.
| Attributes | |
| ACN | 473890 |
| Time | |
| Date | 200005 |
| Day | Mon |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| State Reference | NY |
| Altitude | msl single value : 9000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : alb.tracon |
| Operator | general aviation : personal |
| Make Model Name | Baron 58/58TC |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other vortac |
| Flight Phase | cruise : level |
| Route In Use | enroute airway : v487.airway enroute airway : v91.airway |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : multi engine |
| Experience | flight time last 90 days : 90 flight time total : 1880 flight time type : 60 |
| ASRS Report | 473890 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Events | |
| Anomaly | non adherence : clearance non adherence : far other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued alert other |
| Supplementary | |
| Problem Areas | Aircraft Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I was given a 025 degree vector which would take me toward the cambridge VOR. I put in the wrong VOR frequency. Instead of 115.00 I dialed in 115.10 -- chester VOR. At the same time my headset wire got a loose connection and made it difficult to hear until I corrected the problem. The distraction allowed me to miss having dialed in the wrong frequency and I began to turn toward the chester VOR away from the assigned vector. I missed identifying the VOR with the static in my headset and thought I was turning on course. Approach annoyed, told me I had turned to a 110 degree heading and I must get back on the 025 degree heading, which I did. The rest of the IFR trip was uneventful. A lesson in safety to be learned is even a minor distraction -- static in headset, hard to hear, was enough confusion to cause an error as I described. I need to be very alert to results of distrs and continue to xchk everything.
Original NASA ASRS Text
Title: PLT OF A BEECH BE58, TURNED THE WRONG WAY WHEN VECTORED BY ALB APCH CTLR DUE TO TUNING IN THE WRONG VOR FREQ.
Narrative: I WAS GIVEN A 025 DEG VECTOR WHICH WOULD TAKE ME TOWARD THE CAMBRIDGE VOR. I PUT IN THE WRONG VOR FREQ. INSTEAD OF 115.00 I DIALED IN 115.10 -- CHESTER VOR. AT THE SAME TIME MY HEADSET WIRE GOT A LOOSE CONNECTION AND MADE IT DIFFICULT TO HEAR UNTIL I CORRECTED THE PROB. THE DISTR ALLOWED ME TO MISS HAVING DIALED IN THE WRONG FREQ AND I BEGAN TO TURN TOWARD THE CHESTER VOR AWAY FROM THE ASSIGNED VECTOR. I MISSED IDENTIFYING THE VOR WITH THE STATIC IN MY HEADSET AND THOUGHT I WAS TURNING ON COURSE. APCH ANNOYED, TOLD ME I HAD TURNED TO A 110 DEG HDG AND I MUST GET BACK ON THE 025 DEG HDG, WHICH I DID. THE REST OF THE IFR TRIP WAS UNEVENTFUL. A LESSON IN SAFETY TO BE LEARNED IS EVEN A MINOR DISTR -- STATIC IN HEADSET, HARD TO HEAR, WAS ENOUGH CONFUSION TO CAUSE AN ERROR AS I DESCRIBED. I NEED TO BE VERY ALERT TO RESULTS OF DISTRS AND CONTINUE TO XCHK EVERYTHING.
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.