37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1040666 |
Time | |
Date | 201210 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | MYF.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Ground |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Ground Event / Encounter Other / Unknown Ground Incursion Taxiway |
Narrative:
A PA28 was handed off from sct north sector 3 miles from myf. While previously on local control 1 position; sct north sector verbally coordinated that they were going to hold on to communication with the aircraft because the pilot was having a hard time seeing the runway. While conducting my two minute overlap on the local control 1 position; the PA28 called myf on his initial call. The local control 1 controller approved a left 360 degree turn for descent and coordinated a point out with san tower. I concluded my two minute overlap. I was in the back of the tower when I heard the local control 1 controller inform the pilot he was north of the runway 28R center line. I observed the aircraft north of myf center lines heading in a northerly route. The local control 1 controller informed the aircraft that he appeared north of runway 28L and the pilot acknowledged and turned south for runway 28L. The local control 1 issued a landing on runway 28L will be at your own risk to the aircraft. After the aircraft touched down; I observed the aircraft landed on taxiway H instead of runway 28L. I was not on a controller position. The airport has a runway construction project going on for the next month. Runway 28R is the only runway with lights; and is closed due to the construction. The only usable runway 28L has had reflectors installed prior to construction. Solar powered lighting for the runway was to be installed prior to construction starting but is a couple weeks behind schedule. The solar powered lights are not FAA approved. The runway 28L REIL lights were on as well as all taxiway lights. It is impossible to determine if the pilot is over the open runway 28L or over the closed runway 28R or taxiway H until the aircraft is less than 5 feet off the ground due to darkness. Due to the lack of runway lights on any operational runway; I would recommend that the runway be closed at sunset. The eastern half of the airport is completely pitch black with the exception of the taxiway lights including the landing threshold. It is impossible to determine if the pilot is over the open runway 28L or over the closed runway 28R or taxiway H until the aircraft is less than 5 feet off the ground due to darkness. Aircraft have been aligning with the closed runway and are having a very hard time seeing runway 28L even with the REIL's on.
Original NASA ASRS Text
Title: MYF Controller described a taxiway landing event claiming the lack of runway lights due to construction was the primary cause; adding that operations to the subject runway should be curtailed until lighting is provided.
Narrative: A PA28 was handed off from SCT North Sector 3 miles from MYF. While previously on Local Control 1 position; SCT North sector verbally coordinated that they were going to hold on to communication with the aircraft because the pilot was having a hard time seeing the runway. While conducting my two minute overlap on the Local Control 1 position; the PA28 called MYF on his initial call. The Local Control 1 Controller approved a left 360 degree turn for descent and coordinated a point out with SAN Tower. I concluded my two minute overlap. I was in the back of the Tower when I heard the Local Control 1 Controller inform the pilot he was north of the Runway 28R center line. I observed the aircraft north of MYF center lines heading in a northerly route. The Local Control 1 Controller informed the aircraft that he appeared north of Runway 28L and the pilot acknowledged and turned south for Runway 28L. The Local Control 1 issued a landing on Runway 28L will be at your own risk to the aircraft. After the aircraft touched down; I observed the aircraft landed on Taxiway H instead of Runway 28L. I was not on a controller position. The airport has a runway construction project going on for the next month. Runway 28R is the only runway with lights; and is closed due to the construction. The only usable Runway 28L has had reflectors installed prior to construction. Solar powered lighting for the runway was to be installed prior to construction starting but is a couple weeks behind schedule. The solar powered lights are not FAA approved. The Runway 28L REIL lights were on as well as all taxiway lights. It is impossible to determine if the pilot is over the open Runway 28L or over the closed Runway 28R or Taxiway H until the aircraft is less than 5 feet off the ground due to darkness. Due to the lack of runway lights on any operational runway; I would recommend that the runway be closed at sunset. The eastern half of the airport is completely pitch black with the exception of the taxiway lights including the landing threshold. It is impossible to determine if the pilot is over the open Runway 28L or over the closed Runway 28R or Taxiway H until the aircraft is less than 5 feet off the ground due to darkness. Aircraft have been aligning with the closed runway and are having a very hard time seeing Runway 28L even with the REIL's on.
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.