37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 418968 |
Time | |
Date | 199811 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : sna airport : sna |
State Reference | CA |
Altitude | msl bound lower : 4000 msl bound upper : 5000 |
Environment | |
Flight Conditions | Marginal |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tracon : lax |
Operator | general aviation : corporate |
Make Model Name | Super King Air 200/Huron |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach descent other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Challenger CL600 |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 62 flight time total : 11859 flight time type : 1550 |
ASRS Report | 418968 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Miss Distance | horizontal : 6000 vertical : 500 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was being vectored for an ILS approach to sna airport. I was on a heading of 310 degrees at 5000 ft. I was told I was to be vectored across the localizer to runway 19R. About the time I crossed the localizer, I was asked by a passenger to call ahead for a taxi. In doing so, I somehow changed the frequency on the radio I was speaking to approach with by .25 HZ. After 2 or 3 mins passed without hearing any chatter, I started looking to see what might be wrong and discovered the #1 communication was tuned to 121.32 instead of 121.30. When I finally got back with approach I was given a heading of 165 degrees and a descent to 4000 ft. I assumed this heading was to intercept the runway 19R localizer. After a couple of mins, I was given a heading of what I believed to be 130 degrees, thinking this was to get me closer to the localizer. What I have now learned is the heading I was assigned was 030 degrees. What I also know now was after 52 seconds on that 130 degree heading, I was told by the controller 'expedite your left turn to 010 degrees.' nothing more was said regarding this matter and the rest of the approach and landing went smoothly. It wasn't until my departure 1 hour later that I learned of the problem at hand when I was given a phone number to call when I got on the ground in las vegas. It seems my 52 seconds on the 130 degree heading caused a breach of required separation -- whatever that is. I have been told by the socal supervisor on duty last night that when this occurs they are compelled to investigate and if in fact this breach did occur, they must forward their report to the FAA. I guess what I take from this is a loss of communications, dealing with a persistent passenger needing a taxi, and not knowing my exact position (in part due to the communication problem), and my expectation to get on the localizer led to a brief mental lapse where I set 130 degrees on the heading bug instead of 030 degrees. What really seems odd to me is socal says they have me on tape reading back 'turn left to 030 degrees.'
Original NASA ASRS Text
Title: CPR PLT OF A BE20 INADVERTENTLY SWITCHES HIS COM FREQ WHEN PAX REQUESTS A TAXI TO MEET THE ACFT. PLT DOES NOT IMMEDIATELY RECOGNIZE THAT HE IS NOT IN CONTACT. WHEN VECTORED HE BELIEVES THE HDG TO BE 130 DEGS WHEN IN FACT IT WAS 030 DEGS. LOSS OF SEPARATION RESULTS.
Narrative: I WAS BEING VECTORED FOR AN ILS APCH TO SNA ARPT. I WAS ON A HDG OF 310 DEGS AT 5000 FT. I WAS TOLD I WAS TO BE VECTORED ACROSS THE LOC TO RWY 19R. ABOUT THE TIME I CROSSED THE LOC, I WAS ASKED BY A PAX TO CALL AHEAD FOR A TAXI. IN DOING SO, I SOMEHOW CHANGED THE FREQ ON THE RADIO I WAS SPEAKING TO APCH WITH BY .25 HZ. AFTER 2 OR 3 MINS PASSED WITHOUT HEARING ANY CHATTER, I STARTED LOOKING TO SEE WHAT MIGHT BE WRONG AND DISCOVERED THE #1 COM WAS TUNED TO 121.32 INSTEAD OF 121.30. WHEN I FINALLY GOT BACK WITH APCH I WAS GIVEN A HDG OF 165 DEGS AND A DSCNT TO 4000 FT. I ASSUMED THIS HDG WAS TO INTERCEPT THE RWY 19R LOC. AFTER A COUPLE OF MINS, I WAS GIVEN A HDG OF WHAT I BELIEVED TO BE 130 DEGS, THINKING THIS WAS TO GET ME CLOSER TO THE LOC. WHAT I HAVE NOW LEARNED IS THE HDG I WAS ASSIGNED WAS 030 DEGS. WHAT I ALSO KNOW NOW WAS AFTER 52 SECONDS ON THAT 130 DEG HDG, I WAS TOLD BY THE CTLR 'EXPEDITE YOUR L TURN TO 010 DEGS.' NOTHING MORE WAS SAID REGARDING THIS MATTER AND THE REST OF THE APCH AND LNDG WENT SMOOTHLY. IT WASN'T UNTIL MY DEP 1 HR LATER THAT I LEARNED OF THE PROB AT HAND WHEN I WAS GIVEN A PHONE NUMBER TO CALL WHEN I GOT ON THE GND IN LAS VEGAS. IT SEEMS MY 52 SECONDS ON THE 130 DEG HDG CAUSED A BREACH OF REQUIRED SEPARATION -- WHATEVER THAT IS. I HAVE BEEN TOLD BY THE SOCAL SUPVR ON DUTY LAST NIGHT THAT WHEN THIS OCCURS THEY ARE COMPELLED TO INVESTIGATE AND IF IN FACT THIS BREACH DID OCCUR, THEY MUST FORWARD THEIR RPT TO THE FAA. I GUESS WHAT I TAKE FROM THIS IS A LOSS OF COMS, DEALING WITH A PERSISTENT PAX NEEDING A TAXI, AND NOT KNOWING MY EXACT POS (IN PART DUE TO THE COM PROB), AND MY EXPECTATION TO GET ON THE LOC LED TO A BRIEF MENTAL LAPSE WHERE I SET 130 DEGS ON THE HDG BUG INSTEAD OF 030 DEGS. WHAT REALLY SEEMS ODD TO ME IS SOCAL SAYS THEY HAVE ME ON TAPE READING BACK 'TURN L TO 030 DEGS.'
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.