Myf tower controllers reported a runway incursion citing that a lack of runway markings and minimal ...

Attributes
ACN	1426853
Time
Date	201702
Local Time Of Day	1201-1800
Place
Locale Reference	MYF.Tower
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
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
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2
Person 2
Function	Ground Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 8
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway

Narrative:

LC1 and LC2 were split and I was working LC1. Traffic was busy. Aircraft Y was just crossing the runway threshold to land when I and the other local control controller observed aircraft X turn onto the active runway which aircraft Y was landing on. The other local control controller quickly instructed aircraft X to exit the runway. The LC2 controller gave aircraft X hold instructions which he read back correctly. He then continued to turn onto the active runway witch he was told to hold short off. I believe this happened because he had exited onto our intersecting runway which has no lines on it to show where the parallel runway edge lines should be. Another contributing factor is that ground control was combined with controller in charge (which is an everyday event) so there was one less set of eyes over the operation witch decreases the safety culture here at myf.we have no flms so I would recommend getting some flms so that ground control is not combined with controller in charge witch takes away from the operation and is a safety issue. I recommend that we be considered here at myf to be slated with more controllers. This would help elevate with the high volume of traffic that we face daily while being staffed to the minimums nearly every day.

Original NASA ASRS Text

Title: MYF Tower Controllers reported a runway incursion citing that a lack of runway markings and minimal staffing attributed to the incursion.

Narrative: LC1 and LC2 were split and I was working LC1. Traffic was busy. Aircraft Y was just crossing the runway threshold to land when I and the other LC controller observed Aircraft X turn onto the active runway which Aircraft Y was landing on. The other LC controller quickly instructed Aircraft X to exit the runway. The LC2 controller gave Aircraft X hold instructions which he read back correctly. He then continued to turn onto the active runway witch he was told to hold short off. I believe this happened because he had exited onto our intersecting runway which has no lines on it to show where the parallel runway edge lines should be. Another contributing factor is that GC was combined with CIC (which is an everyday event) so there was one less set of eyes over the operation witch decreases the safety culture here at MYF.We have NO FLMs so I would recommend getting some FLMs so that GC is not combined with CIC witch takes away from the operation and is a safety issue. I recommend that we be considered here at MYF to be slated with more controllers. This would help elevate with the high volume of traffic that we face daily while being staffed to the minimums nearly every day.

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.

Myf tower controllers reported a runway incursion citing that a lack of runway markings and minimal staffing attributed to the incursion.