Taxiing small aircraft gave an erroneous position report after landing. Ground controller did not visually verify position and cleared aircraft across an active runway where another aircraft was cleared for takeoff.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	160094
Time
Date	199010
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : dal
State Reference	TX
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, Low Wing, 1 Eng, Fixed Gear
Flight Phase	ground other : taxi
Flight Plan	None
Aircraft 2
Operator	other
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : takeoff
Person 1
Affiliation	government : faa
Qualification	controller : radar
Experience	controller military : 4 controller non radar : 4 controller radar : 2
ASRS Report	160094
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I observed small aircraft X land on runway 18. Tower controller switched him to ground control. Runways 18 and 13L intersect. One must cross 13L to get to the majority of the FBO's on the airport if they land on 18 or 13R. Light transport Y was cleared for takeoff on runway 13L. Light transport Y taxied out of the runup area as small aircraft X crossed runway 13L approximately 2000' down. Apparently small aircraft X had contacted ground control and given an incorrect position report that made the controller assume ('ass-U-me') that he had landed on runway 13L instead of runway 18. The controller apparently did not scan and locate the aircraft (it was a slow period) and simply told him to 'taxi to parking.' small aircraft X did, and crossed runway 13L on his way. Lull following peak traffic period. Both the tower (local controller) and I observed small aircraft X cross the runway and queried the person 'working' ground control. I don't believe the pilot of light transport Y noticed anything as small aircraft X was well clear of the runway as they began departure roll. Unrpted/undocumented incident.

Original NASA ASRS Text

Title: TAXIING SMA GAVE AN ERRONEOUS POSITION REPORT AFTER LNDG. GND CTLR DID NOT VISUALLY VERIFY POSITION AND CLEARED ACFT ACROSS AN ACTIVE RWY WHERE ANOTHER ACFT WAS CLEARED FOR TKOF.

Narrative: I OBSERVED SMA X LAND ON RWY 18. TWR CTLR SWITCHED HIM TO GND CTL. RWYS 18 AND 13L INTERSECT. ONE MUST CROSS 13L TO GET TO THE MAJORITY OF THE FBO'S ON THE ARPT IF THEY LAND ON 18 OR 13R. LTT Y WAS CLRED FOR TKOF ON RWY 13L. LTT Y TAXIED OUT OF THE RUNUP AREA AS SMA X CROSSED RWY 13L APPROX 2000' DOWN. APPARENTLY SMA X HAD CONTACTED GND CTL AND GIVEN AN INCORRECT POS RPT THAT MADE THE CTLR ASSUME ('ASS-U-ME') THAT HE HAD LANDED ON RWY 13L INSTEAD OF RWY 18. THE CTLR APPARENTLY DID NOT SCAN AND LOCATE THE ACFT (IT WAS A SLOW PERIOD) AND SIMPLY TOLD HIM TO 'TAXI TO PARKING.' SMA X DID, AND CROSSED RWY 13L ON HIS WAY. LULL FOLLOWING PEAK TFC PERIOD. BOTH THE TWR (LCL CTLR) AND I OBSERVED SMA X CROSS THE RWY AND QUERIED THE PERSON 'WORKING' GND CTL. I DON'T BELIEVE THE PLT OF LTT Y NOTICED ANYTHING AS SMA X WAS WELL CLR OF THE RWY AS THEY BEGAN DEP ROLL. UNRPTED/UNDOCUMENTED INCIDENT.

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.