37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 143386 |
Time | |
Date | 199004 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : pia |
State Reference | IL |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : pia |
Make Model Name | Small Aircraft |
Flight Phase | climbout : takeoff landing other |
Flight Plan | VFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
ASRS Report | 143386 |
Person 2 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : non radar |
Events | |
Anomaly | conflict : ground less severe incursion : landing without clearance non adherence : required legal separation |
Independent Detector | other other : unspecified |
Resolutory Action | other |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Miss Distance | unspecified : 3000 vertical : 0 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Error Pilot Deviation |
Narrative:
I was working local control during a 2 runway operation 13/22. Small aircraft X doing touch and go's on runway 22, plus several departures and arrs on runway 13. Ground control had a veh requesting clearance on runway 4/22 to check surface. It was busy enough to have a need to control the pattern of the touch and go aircraft. The touch and go aircraft was cleared for takeoff and then shortly after asked to start his right crosswind (speed and altitude permitting). The ground controller then received clearance on runway 22 for the veh. Later the aircraft was asked to start his base. The next transmission to the aircraft was 'cleared for takeoff.' he never received a clearance to land. This was when the incursion/deviation occurred. It was brought to the FAA's attention from the maintenance manager (who was in the veh). He saw the aircraft coming down the runway as he sat sideways, he pulled off the runway. The pilot stated the next day that he never saw the veh on the runway as he landed. I did not realize this had happened until it was brought to our attention from the maintenance manager.
Original NASA ASRS Text
Title: SMA X LANDED ON OCCUPIED RWY WITHOUT CLRNC. PLT DEVIATION. LCL CTLR CLEARED SMA X FOR TKOF ON OCCUPIED RWY. SYSTEM ERROR.
Narrative: I WAS WORKING LCL CTL DURING A 2 RWY OPERATION 13/22. SMA X DOING TOUCH AND GO'S ON RWY 22, PLUS SEVERAL DEPS AND ARRS ON RWY 13. GND CTL HAD A VEH REQUESTING CLRNC ON RWY 4/22 TO CHK SURFACE. IT WAS BUSY ENOUGH TO HAVE A NEED TO CONTROL THE PATTERN OF THE TOUCH AND GO ACFT. THE TOUCH AND GO ACFT WAS CLRED FOR TKOF AND THEN SHORTLY AFTER ASKED TO START HIS RIGHT XWIND (SPD AND ALT PERMITTING). THE GND CTLR THEN RECEIVED CLRNC ON RWY 22 FOR THE VEH. LATER THE ACFT WAS ASKED TO START HIS BASE. THE NEXT XMISSION TO THE ACFT WAS 'CLRED FOR TKOF.' HE NEVER RECEIVED A CLRNC TO LAND. THIS WAS WHEN THE INCURSION/DEVIATION OCCURRED. IT WAS BROUGHT TO THE FAA'S ATTN FROM THE MAINT MGR (WHO WAS IN THE VEH). HE SAW THE ACFT COMING DOWN THE RWY AS HE SAT SIDEWAYS, HE PULLED OFF THE RWY. THE PLT STATED THE NEXT DAY THAT HE NEVER SAW THE VEH ON THE RWY AS HE LANDED. I DID NOT REALIZE THIS HAD HAPPENED UNTIL IT WAS BROUGHT TO OUR ATTN FROM THE MAINT MGR.
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.