 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot reported confusion while approaching bis from the east having heard ATIS report runway 13 in use and then the controller's clearance to proceed to jekan thirteen miles northwest of runway 13 for a visual. The controller actually cleared them to the NDB jadan; 5.5 miles southeast for a runway 31 visual.
| Attributes | |
| ACN | 1181607 |
| Time | |
| Date | 201406 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BIS.Airport |
| State Reference | ND |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Late evening our flight was approaching bis. We had both listened to the ATIS; and with a more or less direct crosswind to 13/31; both thought we heard runway 13 was the active runway. We briefed it; and set up for it. When we checked in we thought the controller had said runway 13 as well. When the controller assigned a direct to fix to get us to the airport under VMC conditions it sounded like it was a fix for [runway] 13. The fixes in question were runway 13's jekan; where we thought we were cleared to; vs. Runway 31's jadan (NDB) where the controller thought we [were] going to. After flying to the fix for about 3 minutes; the controller queried our course. We told him and he advised us that we needed to go to the fix for runway 31. We advised him we had read back to him the jekan fix. [We] then re-entered the jadan fix and flew to it. We requested runway 13 from tower; and adjusted our pattern for [runway] 13; which was no issue whatsoever. There was no other traffic in the airport area; no other traffic was affected; and safety was not compromised; just a bit of confusion; I believe partly by the easy confusion of runway numbers 13 vs. 31; the close sounding fixes; and a long day that was to be a far 117 extension as well. We landed without further incident.
Original NASA ASRS Text
Title: A pilot reported confusion while approaching BIS from the east having heard ATIS report Runway 13 in use and then the Controller's clearance to proceed to JEKAN thirteen miles northwest of Runway 13 for a visual. The Controller actually cleared them to the NDB JADAN; 5.5 miles southeast for a Runway 31 visual.
Narrative: Late evening our flight was approaching BIS. We had both listened to the ATIS; and with a more or less direct crosswind to 13/31; both thought we heard Runway 13 was the active runway. We briefed it; and set up for it. When we checked in we thought the Controller had said Runway 13 as well. When the Controller assigned a direct to fix to get us to the airport under VMC conditions it sounded like it was a fix for [Runway] 13. The fixes in question were Runway 13's JEKAN; where we thought we were cleared to; vs. Runway 31's JADAN (NDB) where the Controller thought we [were] going to. After flying to the fix for about 3 minutes; the Controller queried our course. We told him and he advised us that we needed to go to the fix for Runway 31. We advised him we had read back to him the JEKAN fix. [We] then re-entered the JADAN fix and flew to it. We requested Runway 13 from Tower; and adjusted our pattern for [Runway] 13; which was no issue whatsoever. There was no other traffic in the airport area; no other traffic was affected; and safety was not compromised; just a bit of confusion; I believe partly by the easy confusion of runway numbers 13 vs. 31; the close sounding fixes; and a long day that was to be a FAR 117 extension as well. We landed without further incident.
Data retrieved from NASA's ASRS site 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.