37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1492111 |
Time | |
Date | 201710 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | BET.Airport |
State Reference | AK |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Check Pilot Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Descended with radar for visual approach to bet. I had previously asked what MVA was in the bethel area. I recall something around 3000 ft was given. After asking for a descent for visual; at about 5200 ft ATC advised 'radar contact lost'. Below clouds with lowest layer about 3100 ft AGL; saw a well-lit runway on approximately the correct orientation for bet 19. PF (pilot flying) and pm (pilot monitoring) concurred runway in sight. We had runway lights for a north/south runway in sight; with PAPI. These were very bright. After beginning visual final with tower; tower stated 'not in sight; cleared to land'. Tower stated lights were on high; and these seemed to be set high.established on final; both pilots questioned the runway; lack of parallel and cross. Executed a go-around and turned west with town of bethel in sight. Airport was visually acquired; normal landing at bet.after landing the airport we initially saw was determined to be kwethluk kwt runway 18/36. This airport has pilot controlled lighting. I never saw it illuminated on previous arrivals. [I recommend] authorized use of 'own ship' position in class 1 efb operation. Flight crew may have been better served to conduct published approach to the planned destination. Should have asked tower to switch light off then back on. This would have been more definitive than just the runway lights are on full bright.
Original NASA ASRS Text
Title: Air Carrier Crew reported lining up with the wrong runway at a nearby airport at night.
Narrative: Descended with radar for visual approach to BET. I had previously asked what MVA was in the Bethel area. I recall something around 3000 ft was given. After asking for a descent for visual; at about 5200 ft ATC advised 'radar contact lost'. Below clouds with lowest layer about 3100 ft AGL; Saw a well-lit runway on approximately the correct orientation for BET 19. PF (Pilot Flying) and PM (Pilot Monitoring) concurred runway in sight. We had runway lights for a north/south runway in sight; with PAPI. These were very bright. After beginning visual final with tower; tower stated 'not in sight; cleared to land'. Tower stated lights were on high; and these seemed to be set high.Established on final; both pilots questioned the runway; lack of parallel and cross. Executed a go-around and turned west with town of Bethel in sight. Airport was visually acquired; normal landing at BET.After landing the airport we initially saw was determined to be Kwethluk KWT RWY 18/36. This airport has pilot controlled lighting. I never saw it illuminated on previous arrivals. [I recommend] authorized use of 'own ship' position in Class 1 EFB operation. Flight crew may have been better served to conduct published approach to the planned destination. Should have asked tower to switch light off then back on. This would have been more definitive than just the runway lights are on full bright.
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.