PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Air Traffic Control Fully Certified
ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Other / Unknown; Ground Incursion Taxiway
General None Reported / Taken
Procedure; Human Factors; Airport; Environment - Non Weather Related
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.
I was on Ground Control and looking out the window listening to the Local Controller instructing a pilot on the location of Runway 28L. The aircraft appeared north of the flight path both Runway 28R and Runway 28L. As instructions were given the pilot appeared to be re-correcting and lining up for Runway 28L. It was only until roll out that it was apparent that the aircraft landed on Hotel Taxiway. This landing occurred during night time operations. The aircraft made an approach to an unlit runway during night time operations. Pilots have been landing at their own risk to Runway 28L (at night). I would recommend no landings or departures be conducted on the runway during night time operations until the temporary lights are installed.
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.