 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Cpr mdt unauthorized landing at bos causes air carrier go around.
| Attributes | |
| ACN | 91728 |
| Time | |
| Date | 198807 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : bos |
| State Reference | MA |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : bos tower : bos |
| Operator | general aviation : corporate |
| Make Model Name | Medium Transport |
| Flight Phase | landing other |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | descent : approach landing : go around |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 200 flight time total : 7200 flight time type : 300 |
| ASRS Report | 91728 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 150 flight time total : 11464 flight time type : 3000 |
| ASRS Report | 91727 |
| Events | |
| Anomaly | incursion : landing without clearance non adherence : clearance non adherence : far |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact none taken : unable |
| Consequence | faa : investigated faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 0 vertical : 1000 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
While on approach to the ILS 22L at bos we were in continuous radio contact with the approach controller. We were given headings to intercept the final approach path and also to hold short of an intersecting runway (27). We acknowledged all transmissions to controllers, provided adequate sep between ourselves and the widebody transport we were following. During this period, traffic was very heavy and controllers were departing and landing traffic on different intersecting runways. We were told to hold short of runway 27 at least 3 times, each time we responded and read back the directive. Upon landing we did hold short of runway 27 but did not make the second high speed turnoff we had wanted to (we were not told to do this however). At this time the tower controller started saying we were no radio and we caused 3 other airplanes to go-around. After landing we did not move hoping to get instruction from the controller (tower). I tried to call him but all my attempts were stepped on by other controller conversation or pilot conversation. Finally we were instructed to do a '180' and clear the runway, I believe the problem may have been eliminated somewhat by better approach control and tower communication. An air carrier pilot behind us had to go-around, but that was probable anyway because we did not have instruction while on the runway as to what to do. I sincerely regret this occurrence but do not feel we as a crew did anything out of line. Callback conversation with reporter revealed following information. The first officer is sure he did not call the tower until after landing. The incident is still with the bos FSDO and the flight crew has not heard from them yet. First officer says he was talking to the approach controller until close in and thinks there could have been better coordination between the tower and TRACON. Says he tried to get the PIC PF to make the second high speed but he was so intent on a smooth landing that he let the aircraft float too far.
Original NASA ASRS Text
Title: CPR MDT UNAUTH LNDG AT BOS CAUSES ACR GO AROUND.
Narrative: WHILE ON APCH TO THE ILS 22L AT BOS WE WERE IN CONTINUOUS RADIO CONTACT WITH THE APCH CTLR. WE WERE GIVEN HDGS TO INTERCEPT THE FINAL APCH PATH AND ALSO TO HOLD SHORT OF AN INTERSECTING RWY (27). WE ACKNOWLEDGED ALL TRANSMISSIONS TO CTLRS, PROVIDED ADEQUATE SEP BTWN OURSELVES AND THE WDB WE WERE FOLLOWING. DURING THIS PERIOD, TFC WAS VERY HEAVY AND CTLRS WERE DEPARTING AND LNDG TFC ON DIFFERENT INTERSECTING RWYS. WE WERE TOLD TO HOLD SHORT OF RWY 27 AT LEAST 3 TIMES, EACH TIME WE RESPONDED AND READ BACK THE DIRECTIVE. UPON LNDG WE DID HOLD SHORT OF RWY 27 BUT DID NOT MAKE THE SECOND HIGH SPD TURNOFF WE HAD WANTED TO (WE WERE NOT TOLD TO DO THIS HOWEVER). AT THIS TIME THE TWR CTLR STARTED SAYING WE WERE NO RADIO AND WE CAUSED 3 OTHER AIRPLANES TO GO-AROUND. AFTER LNDG WE DID NOT MOVE HOPING TO GET INSTRUCTION FROM THE CTLR (TWR). I TRIED TO CALL HIM BUT ALL MY ATTEMPTS WERE STEPPED ON BY OTHER CTLR CONVERSATION OR PLT CONVERSATION. FINALLY WE WERE INSTRUCTED TO DO A '180' AND CLR THE RWY, I BELIEVE THE PROB MAY HAVE BEEN ELIMINATED SOMEWHAT BY BETTER APCH CTL AND TWR COM. AN ACR PLT BEHIND US HAD TO GO-AROUND, BUT THAT WAS PROBABLE ANYWAY BECAUSE WE DID NOT HAVE INSTRUCTION WHILE ON THE RWY AS TO WHAT TO DO. I SINCERELY REGRET THIS OCCURRENCE BUT DO NOT FEEL WE AS A CREW DID ANYTHING OUT OF LINE. CALLBACK CONVERSATION WITH RPTR REVEALED FOLLOWING INFO. THE F/O IS SURE HE DID NOT CALL THE TWR UNTIL AFTER LNDG. THE INCIDENT IS STILL WITH THE BOS FSDO AND THE FLT CREW HAS NOT HEARD FROM THEM YET. F/O SAYS HE WAS TALKING TO THE APCH CTLR UNTIL CLOSE IN AND THINKS THERE COULD HAVE BEEN BETTER COORD BTWN THE TWR AND TRACON. SAYS HE TRIED TO GET THE PIC PF TO MAKE THE SECOND HIGH SPD BUT HE WAS SO INTENT ON A SMOOTH LNDG THAT HE LET THE ACFT FLOAT TOO FAR.
Data retrieved from NASA's ASRS site as of August 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.