<< >> NASA ASRS Report 215288, July 1992

Ground control crossed vehicle in front of small aircraft X takeoff. Small aircraft X had less than standard separation from vehicle. System error.

Attributes
ACN	215288
Time
Date	199207
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : far
State Reference	ND
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	climbout : takeoff
Person 1
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
ASRS Report	215288
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	conflict : ground less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 3000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Inter Facility Coordination Failure

Narrative:

I was working ground control with runways 3 and 35 active. Runway 3 had been returned to local control's use when 5 min later a military vehicle called to cross runway 3. I gave the vehicle permission to cross. Just as small aircraft X was lifting off the runway upfield, the vehicle was already across the runway when it was discovered and no evasive actions needed. This runway is crossed many times a day by the military and on ground control it becomes automatic to cross when they call (the runway is seldom active). When this occurred we also had a tornado 10 mi northwest of the airport and I let that and other duties distract me from the fact that runway 3 was active. If there were better visual reminders that the runway was active or if the military went around their perimeter road for routine activity the chances of this happening again could be decreased. Controllers must be aware of every decision.

Related reports:

• Less than legal separation for 2 aircraft in ZKC positive co...
• Light transport had loss of aircraft control possible less t...
• In trail separation criterion not met behind a B-757. Tempor...
• Radar separation was lost when an aircraft was descened to a...
• Aircraft X was given a clearance by control 1 to climb above...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: GND CTL CROSSED VEHICLE IN FRONT OF SMA X TKOF. SMA X HAD LTSS FROM VEHICLE. SYS ERROR.

Narrative: I WAS WORKING GND CTL WITH RWYS 3 AND 35 ACTIVE. RWY 3 HAD BEEN RETURNED TO LCL CTL'S USE WHEN 5 MIN LATER A MIL VEHICLE CALLED TO CROSS RWY 3. I GAVE THE VEHICLE PERMISSION TO CROSS. JUST AS SMA X WAS LIFTING OFF THE RWY UPFIELD, THE VEHICLE WAS ALREADY ACROSS THE RWY WHEN IT WAS DISCOVERED AND NO EVASIVE ACTIONS NEEDED. THIS RWY IS CROSSED MANY TIMES A DAY BY THE MIL AND ON GND CTL IT BECOMES AUTOMATIC TO CROSS WHEN THEY CALL (THE RWY IS SELDOM ACTIVE). WHEN THIS OCCURRED WE ALSO HAD A TORNADO 10 MI NW OF THE ARPT AND I LET THAT AND OTHER DUTIES DISTRACT ME FROM THE FACT THAT RWY 3 WAS ACTIVE. IF THERE WERE BETTER VISUAL REMINDERS THAT THE RWY WAS ACTIVE OR IF THE MIL WENT AROUND THEIR PERIMETER ROAD FOR ROUTINE ACTIVITY THE CHANCES OF THIS HAPPENING AGAIN COULD BE DECREASED. CTLRS MUST BE AWARE OF EVERY DECISION.

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.