 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pvd controller reports of an aircraft not talking to approach or tower lands opposite direction with a carrier on final to the landing runway. Carrier was sent around and controllers attempted to talk to landing aircraft but there was no answer. Aircraft taxied to parking and was met by airport operations. Asde-X did not alarm.
| Attributes | |
| ACN | 1266225 |
| Time | |
| Date | 201505 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | PVD.Airport |
| State Reference | RI |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Landing |
| Route In Use | None |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.5 |
| Events | |
| Anomaly | Airspace Violation All Types Conflict Ground Conflict Less Severe Deviation - Procedural Landing Without Clearance Deviation - Procedural Clearance Deviation - Procedural FAR Ground Incursion Runway |
Narrative:
During a tfr event at the oqu airport with a few restrictions in place. Aircraft X; not talking to pvd approach control or pvd tower landed at pvd on runway 5. The aircraft was not in communication with any personnel at the pvd facility. I was working tower clearance and another controller was on local/ground/controller in charge combined. He had an air carrier aircraft from the arrival controller; cleared him to land. After he was cleared to land the local controller (local control)/ground controller (ground control) scanned the runway and noticed aircraft X was nearly touched down. He immediately asked who is that guy? I immediately picked up the phone to call downstairs and reported that we had an aircraft land opposite direction runway 5. The local control/ground control then canceled the air carriers landing clearance and I told him to put him on a 140 heading maintain 2;000 feet. We tried to contact aircraft X several times on the tower; ground and guard frequencies numerous times. The aircraft taxied to the ramp and was met by airport operations. The asde-X did not go off and no loss of separation occurred. No recommendations. Keep scanning.
Original NASA ASRS Text
Title: PVD Controller reports of an aircraft not talking to approach or Tower lands opposite direction with a carrier on final to the landing runway. Carrier was sent around and controllers attempted to talk to landing aircraft but there was no answer. Aircraft taxied to parking and was met by airport operations. ASDE-X did not alarm.
Narrative: During a TFR event at the OQU airport with a few restrictions in place. Aircraft X; not talking to PVD approach control or PVD tower landed at PVD on Runway 5. The aircraft was not in communication with any personnel at the PVD facility. I was working Tower Clearance and another controller was on Local/Ground/CIC combined. He had an air carrier aircraft from the arrival controller; cleared him to land. After he was cleared to land the Local Controller (LC)/Ground Controller (GC) scanned the runway and noticed Aircraft X was nearly touched down. He immediately asked who is that guy? I immediately picked up the phone to call downstairs and reported that we had an aircraft land opposite direction Runway 5. The LC/GC then canceled the air carriers landing clearance and I told him to put him on a 140 heading maintain 2;000 feet. We tried to contact Aircraft X several times on the tower; ground and guard frequencies numerous times. The aircraft taxied to the ramp and was met by airport operations. The ASDE-X did not go off and no loss of separation occurred. No recommendations. Keep scanning.
Data retrieved from NASA's ASRS site 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.