Cma controller described runway incursion event during a runway change procedure; reporter recommend...

Narrative:

The event occurred during a change from runway 8 to runway 26. Traffic was steady and for about 10 minutes both runway's 8 and 26 were used to depart aircraft that were already in the run-up for the respective runways. I was trying to maintain a heightened state of awareness at this time because of the runway change. Aircraft X was the last departure for runway 8. The local control cleared aircraft X for takeoff from runway 8. I heard him reply cleared for takeoff. What I did not hear was aircraft Y who had been told to stand by previously at runway 26 also respond he was cleared for takeoff. After the local control cleared aircraft X for departure off runway 8 the controller asked an inbound transponder only aircraft to say altitude because of traffic on the downwind departure. Then we noticed that aircraft Y was across the hold line for runway 26. The local control told aircraft Y he was not cleared for takeoff and to make a 180 to exit the safety area and then she canceled takeoff clearance and told him to hold his position. When aircraft Y exited the safety area the local control then cleared aircraft X for departure from runway 8. I think a way to avoid this in the future is to have a set of racl (runway access control lights) lights at every entry point to a runway to visually tell the pilot he may access the runway. You could also hook up some type of motion sensor so that when something crosses the hold line the light returns to a red X. That way he will have to have audible and visual conformation that he may enter the runway; not only for departure but also for crossing. A tape review indicated I was too loud in the background when the local controller was transmitting during the time leading up to the runway change. I will in the future try to lower my projection so as to not be background noise while others are transmitting.

Original NASA ASRS Text

Title: CMA Controller described runway incursion event during a runway change procedure; reporter recommending additional runway access lighting equipment to provide pilots with increased information.

Narrative: The event occurred during a change from Runway 8 to Runway 26. Traffic was steady and for about 10 minutes both Runway's 8 and 26 were used to depart aircraft that were already in the run-up for the respective runways. I was trying to maintain a heightened state of awareness at this time because of the runway change. Aircraft X was the last departure for Runway 8. The Local Control cleared Aircraft X for takeoff from Runway 8. I heard him reply cleared for takeoff. What I did not hear was Aircraft Y who had been told to stand by previously at Runway 26 also respond he was cleared for takeoff. After the Local Control cleared Aircraft X for departure off Runway 8 the Controller asked an inbound transponder only aircraft to say ALT because of traffic on the downwind departure. Then we noticed that Aircraft Y was across the hold line for Runway 26. The Local Control told Aircraft Y he was not cleared for takeoff and to make a 180 to exit the safety area and then she canceled takeoff clearance and told him to hold his position. When Aircraft Y exited the safety area the Local Control then cleared Aircraft X for departure from Runway 8. I think a way to avoid this in the future is to have a set of RACL (Runway Access Control Lights) lights at every entry point to a runway to visually tell the pilot he may access the runway. You could also hook up some type of motion sensor so that when something crosses the hold line the light returns to a RED X. That way he will have to have audible and visual conformation that he may enter the runway; not only for departure but also for crossing. A tape review indicated I was too loud in the background when the Local Controller was transmitting during the time leading up to the runway change. I will in the future try to lower my projection so as to not be background noise while others are transmitting.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	868511
Time
Date	201001
Local Time Of Day	0001-0600
Place
Locale Reference	CMA.Airport
State Reference	CA
Aircraft 1
Make Model Name	Cessna Aircraft Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Flight Plan	VFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Taxi
Person 1
Function	Coordinator
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Single Pilot Pilot Flying
Qualification	Flight Crew Instrument Flight Crew Commercial Flight Crew Multiengine
Experience	Flight Crew Last 90 Days .3 Flight Crew Total 2675 Flight Crew Type 687
Events
Anomaly	Conflict Ground Conflict Less Severe Ground Incursion Runway

Cma controller described runway incursion event during a runway change procedure; reporter recommending additional runway access lighting equipment to provide pilots with increased information.