Air carrier X had less than standard separation from vehicle Y unauthorized runway entry. System err...

Attributes
ACN	163787
Time
Date	199011
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : mke
State Reference	WI
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
ASRS Report	163787
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Experience	controller radar : 8
ASRS Report	164065
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Miss Distance	horizontal : 7000 vertical : 0
Supplementary
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

Air carrier X an large transport had been cleared for takeoff on runway 19R. About the time air carrier X started its takeoff roll, the controller working flight data inquired if the truck crossing runway 19R had a clearance to cross an active runway at taxiway 'south'. I replied negative. When I first saw the truck it was westbound on taxiway 'south' approaching taxiway 'right' well clear of runway 19R. Air carrier X was just passing taxiway 'gg' approximately 200' from the beginning of runway 19R. The truck was not in radio contact with ground or local control and neither position was aware a non radio truck was operating in the vicinity of the runways. The truck xed an active runway west/O clearance or prior coordination via telephone. I am surprised this type of problem does not occur more at milwaukee mitchell airport. County vehs will call to cross runways but it is very rare for them to call to proceed on taxiway which are designated as movement areas which require a clearance. Supplemental information from acn 164065. During relief briefing to assume ground control, a veh was observed crossing runway 19R. Air carrier X was issued takeoff clearance. I observed veh exiting airport area and informed county operations.

Original NASA ASRS Text

Title: ACR X HAD LESS THAN STANDARD SEPARATION FROM VEHICLE Y UNAUTH RWY ENTRY. SYSTEM ERROR.

Narrative: ACR X AN LGT HAD BEEN CLRED FOR TKOF ON RWY 19R. ABOUT THE TIME ACR X STARTED ITS TKOF ROLL, THE CTLR WORKING FLT DATA INQUIRED IF THE TRUCK XING RWY 19R HAD A CLRNC TO CROSS AN ACTIVE RWY AT TXWY 'S'. I REPLIED NEGATIVE. WHEN I FIRST SAW THE TRUCK IT WAS WBND ON TXWY 'S' APCHING TXWY 'R' WELL CLR OF RWY 19R. ACR X WAS JUST PASSING TXWY 'GG' APPROX 200' FROM THE BEGINNING OF RWY 19R. THE TRUCK WAS NOT IN RADIO CONTACT WITH GND OR LCL CTL AND NEITHER POS WAS AWARE A NON RADIO TRUCK WAS OPERATING IN THE VICINITY OF THE RWYS. THE TRUCK XED AN ACTIVE RWY W/O CLRNC OR PRIOR COORD VIA TELEPHONE. I AM SURPRISED THIS TYPE OF PROB DOES NOT OCCUR MORE AT MILWAUKEE MITCHELL ARPT. COUNTY VEHS WILL CALL TO CROSS RWYS BUT IT IS VERY RARE FOR THEM TO CALL TO PROCEED ON TXWY WHICH ARE DESIGNATED AS MOVEMENT AREAS WHICH REQUIRE A CLRNC. SUPPLEMENTAL INFO FROM ACN 164065. DURING RELIEF BRIEFING TO ASSUME GND CTL, A VEH WAS OBSERVED XING RWY 19R. ACR X WAS ISSUED TKOF CLRNC. I OBSERVED VEH EXITING ARPT AREA AND INFORMED COUNTY OPS.

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

Air carrier X had less than standard separation from vehicle Y unauthorized runway entry. System error.