37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1397776 |
Time | |
Date | 201610 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CMH.Airport |
State Reference | OH |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 137 |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 187 Flight Crew Type 7000 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance |
Narrative:
We were operating to cmh. While we were being handled by cmh approach control on 118.2 we received a TCAS RA. We were flying an assigned altitude of 5000 ft and an assigned heading. We had already been vectored for about 5 to 10 minutes in every direction. ATC advised that a cessna was orbiting at 5000 ft in front of us. We did not have visual contact with the traffic; but the traffic appeared on the TCAS display. ATC cleared us next to descend to 4000 ft. I read back the clearance; and simultaneously we received a TCAS RA. We complied with the RA and reported it to TRACON. The controller seemed indifferent. Within three to four minutes; another airliner behind us (call sign) also received an RA due to the cessna. I asked the controller; why they were vectoring us so close to the cessna? The controller became defensive and said that we were cleared to 4000 ft earlier but did not descend. I replied saying; 'no sir; we were given the clearance to 4000 ft; and responded immediately; simultaneously getting the RA.' the controller replied that he did not want to argue; but offered a telephone number to call TRACON after landing. I sent a quick ACARS message to our dispatcher advising him that we received a TCAS RA. After shutting down the aircraft at the gate; I called our dispatcher. I asked him to get the supervisor involved and that I'd like them to call TRACON. The supervisor referred me to the chief pilot on call. I explained to him what happened. He referred me to one of our ATC specialists. I did reach him and explained the event. I saw no reason for ATC to route us into an approach with a VFR aircraft orbiting; especially all the vectors we already received. We should have been moved over a few miles or brought in on the opposite downwind. The ATC specialist called TRACON; and then called me back. ATC told him that it was an aircraft that was doing surveillance; nothing else to add. I still believe the approach controller should have vectored us away from the orbiting traffic; as evidenced by two identical TCAS ras within a few minutes of each other.
Original NASA ASRS Text
Title: B737 flight crew reported responding to a TCAS RA while on approach to CMH.
Narrative: We were operating to CMH. While we were being handled by CMH Approach Control on 118.2 we received a TCAS RA. We were flying an assigned altitude of 5000 ft and an assigned heading. We had already been vectored for about 5 to 10 minutes in every direction. ATC advised that a Cessna was orbiting at 5000 ft in front of us. We did not have visual contact with the traffic; but the traffic appeared on the TCAS Display. ATC cleared us next to descend to 4000 ft. I read back the clearance; and simultaneously we received a TCAS RA. We complied with the RA and reported it to TRACON. The Controller seemed indifferent. Within three to four minutes; another airliner behind us (call sign) also received an RA due to the Cessna. I asked the Controller; why they were vectoring us so close to the Cessna? The Controller became defensive and said that we were cleared to 4000 ft earlier but did not descend. I replied saying; 'No sir; we were given the clearance to 4000 ft; and responded immediately; simultaneously getting the RA.' The Controller replied that he did not want to argue; but offered a telephone number to call TRACON after landing. I sent a quick ACARS message to our Dispatcher advising him that we received a TCAS RA. After shutting down the aircraft at the gate; I called our Dispatcher. I asked him to get the Supervisor involved and that I'd like them to call TRACON. The Supervisor referred me to the Chief Pilot on call. I explained to him what happened. He referred me to one of our ATC Specialists. I did reach him and explained the event. I saw no reason for ATC to route us into an approach with a VFR aircraft orbiting; especially all the vectors we already received. We should have been moved over a few miles or brought in on the opposite downwind. The ATC Specialist called TRACON; and then called me back. ATC told him that it was an aircraft that was doing surveillance; nothing else to add. I still believe the Approach Controller should have vectored us away from the orbiting traffic; as evidenced by two identical TCAS RAs within a few minutes of each other.
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.