 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew and controllers reported that an aircraft lined up for a runway in close proximity to the airport they were intending on landing.
| Attributes | |
| ACN | 1645797 |
| Time | |
| Date | 201905 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PVD.Airport |
| State Reference | RI |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Aircraft X on arrival route inbound to pvd. Initial altitude 11000. Check on descended to 5000. Turned aircraft direct to bevin intersection for the visual approach to runway 34 at pvd. Aircraft X called pvd in sight. I cleared aircraft X for the visual approach to runway 34 and instructed to turn final over bevin for noise abatement. 10 miles south of pvd I instructed aircraft X to contact tower. Numerous other aircraft were on frequency and practice approaches being done. I then started a relief briefing to release the groton and jumpr airspace. At this time the local controller called and reported they sent aircraft X around because they noticed he on short final for oqu airport. They called oqu tower as I was also keying up the line and were already getting the point out. I asked the oqu tower controller if they had them to ship them to [departure]. I then called local and asked them to give the aircraft back to me for re-sequence. I re-identified aircraft X and put them on a 230; and then a 160 heading. I then continued my relief briefing for the south two sectors.I have no recommendations due to this just being a mistake. No procedure changes would impact what happened.
Original NASA ASRS Text
Title: Flight crew and controllers reported that an aircraft lined up for a runway in close proximity to the airport they were intending on landing.
Narrative: Aircraft X on arrival route inbound to PVD. Initial altitude 11000. Check on descended to 5000. Turned aircraft direct to BEVIN intersection for the visual approach to Runway 34 at PVD. Aircraft X called PVD in sight. I cleared Aircraft X for the visual approach to Runway 34 and instructed to turn final over BEVIN for noise abatement. 10 miles south of PVD I instructed Aircraft X to contact Tower. Numerous other aircraft were on frequency and practice approaches being done. I then started a relief briefing to release the Groton and Jumpr airspace. At this time the Local Controller called and reported they sent Aircraft X around because they noticed he on short final for OQU airport. They called OQU Tower as I was also keying up the line and were already getting the point out. I asked the OQU Tower Controller if they had them to ship them to [Departure]. I then called Local and asked them to give the aircraft back to me for re-sequence. I re-identified Aircraft X and put them on a 230; and then a 160 heading. I then continued my relief briefing for the south two sectors.I have no recommendations due to this just being a mistake. No procedure changes would impact what happened.
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.