Narrative:

The incident occurred at the end of an IFR-filed flight. Aircraft was BE58P. Abq approach asked preferred runway (runway 8 or runway 3). I responded 'either -- whichever is easiest for you.' was then given descent and vectors -- initially for runway 3. Also, initially, frequency was reasonably quiet (non-busy). There may also have been a controller change, although I am not certain of this. As the controller began to get busier handling other aircraft, including a B737, I was given vectors heading me almost directly in line with runway 8. I then asked the controller if I was then to land on runway 8. I thought I heard affirmative acknowledgement, and proceeded toward runway 8, descending. During this time, the controller informed me of B737 traffic, and my passenger and I were looking actively for that traffic, but did not see it. The controller ultimately gave me a request to climb and a new vector for downwind pattern for runway 3. A later discussion by phone with abq TRACON, in which the individual had reviewed the tapes, confirmed my query of runway 8 versus runway 3 to the controller, but that 1) the controller said he had not heard that request, and, 2) that the controller had not affirmed that I was to land on runway 8. The TRACON person was genuinely interested in learning the sequence of events and causes of the miscom, as was I. She stated that she would not file a pilot deviation report. We both felt that the immediate cause appeared to be miscom or incomplete communication. Remedy from my stand point appears to be achieve absolute certainly on any ambiguities in communication.

Google
 

Original NASA ASRS Text

Title: COMS PROB POSSIBLE DUE TO A CTLR CHANGE CAUSING CONFUSION BTWN PLT AND CTLR ON RWY TO BE USED FOR LNDG.

Narrative: THE INCIDENT OCCURRED AT THE END OF AN IFR-FILED FLT. ACFT WAS BE58P. ABQ APCH ASKED PREFERRED RWY (RWY 8 OR RWY 3). I RESPONDED 'EITHER -- WHICHEVER IS EASIEST FOR YOU.' WAS THEN GIVEN DSCNT AND VECTORS -- INITIALLY FOR RWY 3. ALSO, INITIALLY, FREQ WAS REASONABLY QUIET (NON-BUSY). THERE MAY ALSO HAVE BEEN A CTLR CHANGE, ALTHOUGH I AM NOT CERTAIN OF THIS. AS THE CTLR BEGAN TO GET BUSIER HANDLING OTHER ACFT, INCLUDING A B737, I WAS GIVEN VECTORS HDG ME ALMOST DIRECTLY IN LINE WITH RWY 8. I THEN ASKED THE CTLR IF I WAS THEN TO LAND ON RWY 8. I THOUGHT I HEARD AFFIRMATIVE ACKNOWLEDGEMENT, AND PROCEEDED TOWARD RWY 8, DSNDING. DURING THIS TIME, THE CTLR INFORMED ME OF B737 TFC, AND MY PAX AND I WERE LOOKING ACTIVELY FOR THAT TFC, BUT DID NOT SEE IT. THE CTLR ULTIMATELY GAVE ME A REQUEST TO CLB AND A NEW VECTOR FOR DOWNWIND PATTERN FOR RWY 3. A LATER DISCUSSION BY PHONE WITH ABQ TRACON, IN WHICH THE INDIVIDUAL HAD REVIEWED THE TAPES, CONFIRMED MY QUERY OF RWY 8 VERSUS RWY 3 TO THE CTLR, BUT THAT 1) THE CTLR SAID HE HAD NOT HEARD THAT REQUEST, AND, 2) THAT THE CTLR HAD NOT AFFIRMED THAT I WAS TO LAND ON RWY 8. THE TRACON PERSON WAS GENUINELY INTERESTED IN LEARNING THE SEQUENCE OF EVENTS AND CAUSES OF THE MISCOM, AS WAS I. SHE STATED THAT SHE WOULD NOT FILE A PLTDEV RPT. WE BOTH FELT THAT THE IMMEDIATE CAUSE APPEARED TO BE MISCOM OR INCOMPLETE COM. REMEDY FROM MY STAND POINT APPEARS TO BE ACHIEVE ABSOLUTE CERTAINLY ON ANY AMBIGUITIES IN COM.

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.