 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
EMB120 flight crew gets confused over approach controller radar vectoring and heading assigned. After a TCASII TA they query controller and get another incorrect heading assigned. Approach controller had their assumed position as north of localizer runway 23R when they were south of it.
| Attributes | |
| ACN | 367010 |
| Time | |
| Date | 199704 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : tys |
| State Reference | TN |
| Altitude | msl bound lower : 4000 msl bound upper : 4000 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : tys tower : tys |
| Operator | common carrier : air carrier |
| Make Model Name | Xingu EMB-121 All Series |
| Operating Under FAR Part | Part 135 |
| Navigation In Use | Other |
| Flight Phase | descent : approach descent other |
| Route In Use | arrival other enroute : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | other : unknown |
| Flight Phase | other |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : cfi pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 90 flight time total : 2000 flight time type : 500 |
| ASRS Report | 367010 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 210 flight time total : 7500 flight time type : 5000 |
| ASRS Report | 367017 |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance other anomaly other other spatial deviation |
| Independent Detector | aircraft equipment other aircraft equipment : unspecified other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance other |
| Consequence | Other |
| Miss Distance | horizontal : 15000 vertical : 550 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation Operational Error other |
Narrative:
The problem arose due to confusion between crew and improper instructions from approach. We were descending through 4000 ft and given a heading of what I believed was 270 degrees. The captain believed the heading was to 170 degrees. The purpose was vectors for runway 23R. While turning to 270 degrees, we received a TA from the TCASII. (Note: a turn to 170 degrees would not intercept the localizer as we were south of the localizer.) we took evasive action and began to turn sbound away from the traffic, as well as stopping our descent. At this time approach issued us a turn to heading 130 degrees. Following that we were given a heading of 210 degrees to intercept. This heading would never intercept as we were south of the localizer. We were then turned over to tower. The tower immediately queried our position and told us we were lining up for runway 23L. At this point the runway was in sight but we were cleared to land on runway 23L instead of runway 23R. We complied. I believe the confusion on the final was due to crew fatigue and the lack of time available to query ATC prior to being handed off. In addition, I believe approach was unaware of our position or mistaken and believed we were north of course rather than south. Supplemental information from acn 367017: being radar vectored for the ILS runway 23R at tys, a miscom occurred between the 2 pilots and the controller. I perceived as instructions to turn to heading 270 degrees. I asked the first officer to verify that this was the correct heading. The controller was busy with other aircraft. I believe that this occurred because the controller was quite busy as well as the flight crew being fatigued from a long 2 day trip.
Original NASA ASRS Text
Title: EMB120 FLC GETS CONFUSED OVER APCH CTLR RADAR VECTORING AND HDG ASSIGNED. AFTER A TCASII TA THEY QUERY CTLR AND GET ANOTHER INCORRECT HDG ASSIGNED. APCH CTLR HAD THEIR ASSUMED POS AS N OF LOC RWY 23R WHEN THEY WERE S OF IT.
Narrative: THE PROB AROSE DUE TO CONFUSION BTWN CREW AND IMPROPER INSTRUCTIONS FROM APCH. WE WERE DSNDING THROUGH 4000 FT AND GIVEN A HDG OF WHAT I BELIEVED WAS 270 DEGS. THE CAPT BELIEVED THE HDG WAS TO 170 DEGS. THE PURPOSE WAS VECTORS FOR RWY 23R. WHILE TURNING TO 270 DEGS, WE RECEIVED A TA FROM THE TCASII. (NOTE: A TURN TO 170 DEGS WOULD NOT INTERCEPT THE LOC AS WE WERE S OF THE LOC.) WE TOOK EVASIVE ACTION AND BEGAN TO TURN SBOUND AWAY FROM THE TFC, AS WELL AS STOPPING OUR DSCNT. AT THIS TIME APCH ISSUED US A TURN TO HDG 130 DEGS. FOLLOWING THAT WE WERE GIVEN A HDG OF 210 DEGS TO INTERCEPT. THIS HDG WOULD NEVER INTERCEPT AS WE WERE S OF THE LOC. WE WERE THEN TURNED OVER TO TWR. THE TWR IMMEDIATELY QUERIED OUR POS AND TOLD US WE WERE LINING UP FOR RWY 23L. AT THIS POINT THE RWY WAS IN SIGHT BUT WE WERE CLRED TO LAND ON RWY 23L INSTEAD OF RWY 23R. WE COMPLIED. I BELIEVE THE CONFUSION ON THE FINAL WAS DUE TO CREW FATIGUE AND THE LACK OF TIME AVAILABLE TO QUERY ATC PRIOR TO BEING HANDED OFF. IN ADDITION, I BELIEVE APCH WAS UNAWARE OF OUR POS OR MISTAKEN AND BELIEVED WE WERE N OF COURSE RATHER THAN S. SUPPLEMENTAL INFO FROM ACN 367017: BEING RADAR VECTORED FOR THE ILS RWY 23R AT TYS, A MISCOM OCCURRED BTWN THE 2 PLTS AND THE CTLR. I PERCEIVED AS INSTRUCTIONS TO TURN TO HDG 270 DEGS. I ASKED THE FO TO VERIFY THAT THIS WAS THE CORRECT HDG. THE CTLR WAS BUSY WITH OTHER ACFT. I BELIEVE THAT THIS OCCURRED BECAUSE THE CTLR WAS QUITE BUSY AS WELL AS THE FLC BEING FATIGUED FROM A LONG 2 DAY TRIP.
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.