37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 328752 |
Time | |
Date | 199602 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : brw |
State Reference | AK |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 280 flight time total : 5000 flight time type : 1000 |
ASRS Report | 328752 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 7000 flight time type : 4000 |
ASRS Report | 328756 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact other |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
At PM00 local barrow FSS shuts down for the night and remotes their frequencys to fairbanks FSS. In addition, runway lighting is switched from FSS control to pilot controled. At 10 NM from barrow at PM35 local we attempted to turn up the runway and approach lights to step 5 by keying the microphone 7 times. The approach lights illuminated brightly, but the runway lights remained on step 1 (dim). Subsequent tries at stepping up the runway lights were unsuccessful. We determined the lights were adequate for a safe landing and did so uneventfully. Callback conversation with reporter revealed the following information: the flight crew was flying a B737-200 combi when they encountered a problem with the runway lights at barrow, alaska. The approach lights would increase in intensity, but the runway lights would not. The flight crew landed with the runway lights at step 1 and informed their operations personnel of the problem. The operations personnel were able to locate an FSS employee and he came to the airport and 'flipped a switch' and the flight crew then had control over the runway lights as well as the approach lights.
Original NASA ASRS Text
Title: THIS FLC COULD NOT CTL THE RWY LIGHTS BY KEYING THE MIKE SO THE RWY LIGHTS REMAINED ON STEP 1. AFTER LNDG THE OPS PERSONNEL CONTACTED AN FSS SPECIALIST WHO CAME TO THE ARPT AND PUT THE RWY LIGHTS IN THE RADIO CTL MODE. AFTER THIS THE FLC WAS ABLE TO CTL THE RWY LIGHT INTENSITY.
Narrative: AT PM00 LCL BARROW FSS SHUTS DOWN FOR THE NIGHT AND REMOTES THEIR FREQS TO FAIRBANKS FSS. IN ADDITION, RWY LIGHTING IS SWITCHED FROM FSS CTL TO PLT CTLED. AT 10 NM FROM BARROW AT PM35 LCL WE ATTEMPTED TO TURN UP THE RWY AND APCH LIGHTS TO STEP 5 BY KEYING THE MIKE 7 TIMES. THE APCH LIGHTS ILLUMINATED BRIGHTLY, BUT THE RWY LIGHTS REMAINED ON STEP 1 (DIM). SUBSEQUENT TRIES AT STEPPING UP THE RWY LIGHTS WERE UNSUCCESSFUL. WE DETERMINED THE LIGHTS WERE ADEQUATE FOR A SAFE LNDG AND DID SO UNEVENTFULLY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE FLC WAS FLYING A B737-200 COMBI WHEN THEY ENCOUNTERED A PROB WITH THE RWY LIGHTS AT BARROW, ALASKA. THE APCH LIGHTS WOULD INCREASE IN INTENSITY, BUT THE RWY LIGHTS WOULD NOT. THE FLC LANDED WITH THE RWY LIGHTS AT STEP 1 AND INFORMED THEIR OPS PERSONNEL OF THE PROB. THE OPS PERSONNEL WERE ABLE TO LOCATE AN FSS EMPLOYEE AND HE CAME TO THE ARPT AND 'FLIPPED A SWITCH' AND THE FLC THEN HAD CTL OVER THE RWY LIGHTS AS WELL AS THE APCH LIGHTS.
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.