37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1068582 |
Time | |
Date | 201302 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ABQ.Airport |
State Reference | NM |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Instructor |
Qualification | Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 300 Flight Crew Total 1300 Flight Crew Type 200 |
Events | |
Anomaly | ATC Issue All Types Ground Incursion Runway |
Narrative:
I am a flight instructor and had an occurrence at abq that I feel should be brought to someone's attention. I was on a multiengine cross country with a commercial student; two hour day and two hour night first leg VFR; second leg IFR. We were being vectored by albuquerque approach control a few minutes before civil twilight. Approach told us to advise them when we had the runway in sight. My student did not see it at that time. He then told us that the runway was at 11 o'clock and to advise when the runway was in sight. My student still did not see the runway. Then approach told us that he was setting us up for a two mile final for runway 3 and again to advise when the runway was in sight. I pointed out to my student where it was; not very visible. My student reported to approach that he had the runway in sight; I don't think that he did. After he said runway in sight; approach said that he would tell tower to turn the runway lights up for us and to let them know if they were too bright. And contact tower. Turning the 2 mile final the lights turned on (I don't think that they were on at all before) and I heard my student say 'oh;' like he was amazed that the runway was that close. I was not sure if they didn't have the lights on by accident or if they were messing with us. It was getting very dark and I could see the black outline of what looked like an unlighted runway. Leaving albuquerque an hour and a half later; we were parked at an FBO and called clearance delivery to get our IFR clearance before engine start. Clearance was talking to other aircraft as departure/ approach. We checked our frequency and it was correct. He told us to hold on so he could find our flight plan while he was talking to other aircraft on approach/departure; gave us our clearance and told us to tell him when we were ready to taxi (did not tell us to contact ground). We started our engines and my student told him on clearance frequency; 'aircraft X is ready to taxi.' clearance told us to 'aircraft X; taxi to runway 8 via kilo echo 1 or just echo 1.' my student looked at me confused because he called us twin diamond. My student couldn't find kilo and asked for progressive taxi. Clearance told us to switch to his frequency on ground for progressive. We switched to ground frequency and he gave us progressive. He asked my student if he saw a large 727 parked in front of him. I noticed that the taxiway lights were not turned on or the taxiway signs. We held short of the runway hold short line on E1 and performed a run-up. We advised him that our run-up was complete and he cleared us for takeoff on runway 8. My student followed the line with our taxiway light; lined up with center of displaced threshold and began advancing the throttles for takeoff. I hit the brakes and pulled his hand off the throttles and showed him that we were not on runway heading. We were lined up for runway 12; not runway 8. We turned left and lined up with runway 8; while lining up on runway 8 my student verified the heading and took off. It seemed like at night on saturdays; clearance delivery; is ground; tower; and approach/departure. They also seem to be having runway/taxiway lighting problems. They keep turning the lights on and off. There is also only one hold short line for two runways with headings that are forty degrees off from each other. It seems like an unfamiliar pilot could possibly have a runway incursion at this airport.
Original NASA ASRS Text
Title: An Instructor Pilot reported ABQ ATC seemed overloaded on a Saturday night and while acting as the TRACON. Ground Control and Tower was not aware of the lack of airport lighting during dusk and night conditions.
Narrative: I am a flight instructor and had an occurrence at ABQ that I feel should be brought to someone's attention. I was on a multiengine cross country with a commercial student; two hour day and two hour night first leg VFR; second leg IFR. We were being vectored by Albuquerque Approach Control a few minutes before civil twilight. Approach told us to advise them when we had the runway in sight. My student did not see it at that time. He then told us that the runway was at 11 o'clock and to advise when the runway was in sight. My student still did not see the runway. Then Approach told us that he was setting us up for a two mile final for Runway 3 and again to advise when the runway was in sight. I pointed out to my student where it was; not very visible. My student reported to Approach that he had the runway in sight; I don't think that he did. After he said runway in sight; Approach said that he would tell Tower to turn the runway lights up for us and to let them know if they were too bright. And contact Tower. Turning the 2 mile final the lights turned on (I don't think that they were on at all before) and I heard my student say 'OH;' like he was amazed that the runway was that close. I was not sure if they didn't have the lights on by accident or if they were messing with us. It was getting very dark and I could see the black outline of what looked like an unlighted runway. Leaving Albuquerque an hour and a half later; we were parked at an FBO and called Clearance Delivery to get our IFR clearance before engine start. Clearance was talking to other aircraft as Departure/ Approach. We checked our frequency and it was correct. He told us to hold on so he could find our flight plan while he was talking to other aircraft on Approach/Departure; gave us our clearance and told us to tell him when we were ready to taxi (did not tell us to contact ground). We started our engines and my student told him on clearance frequency; 'Aircraft X is ready to taxi.' Clearance told us to 'Aircraft X; taxi to Runway 8 via Kilo Echo 1 or just Echo 1.' My student looked at me confused because he called us twin diamond. My student couldn't find Kilo and asked for progressive taxi. Clearance told us to switch to his frequency on Ground for progressive. We switched to Ground frequency and he gave us progressive. He asked my student if he saw a large 727 parked in front of him. I noticed that the taxiway lights were not turned on or the taxiway signs. We held short of the runway hold short line on E1 and performed a run-up. We advised him that our run-up was complete and he cleared us for takeoff on Runway 8. My student followed the line with our taxiway light; lined up with center of displaced threshold and began advancing the throttles for takeoff. I hit the brakes and pulled his hand off the throttles and showed him that we were not on runway heading. We were lined up for Runway 12; not Runway 8. We turned left and lined up with Runway 8; while lining up on Runway 8 my student verified the heading and took off. It seemed like at night on Saturdays; Clearance Delivery; is Ground; Tower; and Approach/Departure. They also seem to be having runway/taxiway lighting problems. They keep turning the lights on and off. There is also only one hold short line for two runways with headings that are forty degrees off from each other. It seems like an unfamiliar pilot could possibly have a runway incursion at this airport.
Data retrieved from NASA's ASRS site as of July 2013 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.