 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Clt TRACON controller described event when air carrier arrival was expected on RNAV STAR as indicated on data block but executed different procedure.
| Attributes | |
| ACN | 784235 |
| Time | |
| Date | 200804 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : clt.airport |
| State Reference | NC |
| Altitude | msl single value : 9000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : clt.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | arrival star : shine 5 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Experience | controller radar : 22 |
| ASRS Report | 784234 |
| Person 2 | |
| Affiliation | company : air carrier |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Company ATC Human Performance |
| Primary Problem | Ambiguous |
Narrative:
Aircraft X on my information on my stars; said he was on RNAV arrival. I expected him to turn to the downwind about 10 mi southwest of clt. He did not. This creates a hazardous situation; when controllers expect aircraft to do one thing and direct their attention elsewhere only to look back and find the aircraft not doing what he is supposed to. I asked pilot; 'are you on RNAV arrival?' he said 'we were issued 'shine 5' arrival at ord.' (the strip said 'JOHNS1' arrival; as did the stars information on my scope -- JOHNS1 is the RNAV arrival by the way.) I told supervisor; but I don't believe he did anything (called center; put it in log; etc). I am not requesting that anyone 'hang' for this mistake; just desire some type of procedure for looking into this; and any matter like it that occurs that needs to be followed up on. Controllers report things; but that's where the 'ball is dropped' and goes no further.
Original NASA ASRS Text
Title: CLT TRACON CTLR DESCRIBED EVENT WHEN ACR ARR WAS EXPECTED ON RNAV STAR AS INDICATED ON DATA BLOCK BUT EXECUTED DIFFERENT PROC.
Narrative: ACFT X ON MY INFO ON MY STARS; SAID HE WAS ON RNAV ARR. I EXPECTED HIM TO TURN TO THE DOWNWIND ABOUT 10 MI SW OF CLT. HE DID NOT. THIS CREATES A HAZARDOUS SITUATION; WHEN CTLRS EXPECT ACFT TO DO ONE THING AND DIRECT THEIR ATTN ELSEWHERE ONLY TO LOOK BACK AND FIND THE ACFT NOT DOING WHAT HE IS SUPPOSED TO. I ASKED PLT; 'ARE YOU ON RNAV ARR?' HE SAID 'WE WERE ISSUED 'SHINE 5' ARR AT ORD.' (THE STRIP SAID 'JOHNS1' ARR; AS DID THE STARS INFO ON MY SCOPE -- JOHNS1 IS THE RNAV ARR BY THE WAY.) I TOLD SUPVR; BUT I DON'T BELIEVE HE DID ANYTHING (CALLED CTR; PUT IT IN LOG; ETC). I AM NOT REQUESTING THAT ANYONE 'HANG' FOR THIS MISTAKE; JUST DESIRE SOME TYPE OF PROC FOR LOOKING INTO THIS; AND ANY MATTER LIKE IT THAT OCCURS THAT NEEDS TO BE FOLLOWED UP ON. CTLRS RPT THINGS; BUT THAT'S WHERE THE 'BALL IS DROPPED' AND GOES NO FURTHER.
Data retrieved from NASA's ASRS site as of May 2009 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.