37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 595981 |
Time | |
Date | 200310 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : pvd.airport |
State Reference | RI |
Altitude | msl single value : 600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pvd.tracon tower : pvd.tower |
Operator | general aviation : personal |
Make Model Name | Cessna 150 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tower : pvd.tower |
Operator | common carrier : air carrier |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | landing : go around |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 60 flight time total : 312 flight time type : 100 |
ASRS Report | 595981 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : separated traffic flight crew : executed go around |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
Aircraft #1 on approach vector in pvd class C airspace. Aircraft #1 had established radio contact with approach controller. After initial contact, aircraft #1 repeatedly attempted to contact approach controller. All attempts were met with silence. Aircraft #1 flew last assigned heading to within 1/4 mi of pvd. At this point, aircraft #1 was still on approach frequency, never being handed over to pvd tower. Approach controller suddenly reappeared on frequency and vectored aircraft #1 across final course of runway 23. This vector put aircraft #1 in a dangerous situation with aircraft #2 on final for runway 23. I believe aircraft #2 initiated a go around because of these actions. The chain of events could have been prevented had the approach controller: 1) handed aircraft #1 over to tower in a timely manner, 2) replied to the repeated contact attempts by aircraft #1, and 3) turned aircraft #1 away from the final approach course, not through it.
Original NASA ASRS Text
Title: PLT OF C150 HAS CLOSE ENCOUNTER WITH B757 ON APCH TO PVD WHEN APCH CTL IS UNABLE TO COMMUNICATE IN A TIMELY FASHION AFTER HE CHKED INTO THEIR AIRSPACE.
Narrative: ACFT #1 ON APCH VECTOR IN PVD CLASS C AIRSPACE. ACFT #1 HAD ESTABLISHED RADIO CONTACT WITH APCH CTLR. AFTER INITIAL CONTACT, ACFT #1 REPEATEDLY ATTEMPTED TO CONTACT APCH CTLR. ALL ATTEMPTS WERE MET WITH SILENCE. ACFT #1 FLEW LAST ASSIGNED HEADING TO WITHIN 1/4 MI OF PVD. AT THIS POINT, ACFT #1 WAS STILL ON APCH FREQ, NEVER BEING HANDED OVER TO PVD TWR. APCH CTLR SUDDENLY REAPPEARED ON FREQ AND VECTORED ACFT #1 ACROSS FINAL COURSE OF RWY 23. THIS VECTOR PUT ACFT #1 IN A DANGEROUS SIT WITH ACFT #2 ON FINAL FOR RWY 23. I BELIEVE ACFT #2 INITIATED A GAR BECAUSE OF THESE ACTIONS. THE CHAIN OF EVENTS COULD HAVE BEEN PREVENTED HAD THE APCH CTLR: 1) HANDED ACFT #1 OVER TO TWR IN A TIMELY MANNER, 2) REPLIED TO THE REPEATED CONTACT ATTEMPTS BY ACFT #1, AND 3) TURNED ACFT #1 AWAY FROM THE FINAL APCH COURSE, NOT THROUGH IT.
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.