37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 538998 |
Time | |
Date | 200202 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : clt.airport |
State Reference | NC |
Altitude | msl single value : 22000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl.artcc |
Operator | common carrier : air carrier |
Make Model Name | Fokker 100 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 20 flight time total : 10 |
ASRS Report | 538898 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Navigational Facility FAA ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure |
Situations | |
ATC Facility | computer equipment : zid.artcc procedure or policy : zid.artcc |
Narrative:
Air carrier X, an F100, was cleared to cross the shine intersection at 12000 ft and 250 KTS per LOA with ZTL/clt. The pilot asked if he could speed up now, or if I wanted him to wait until shine. It turns out the pilot was assigned 220 KTS coming out of cmh. The pilot relayed that he was asked his speed and replied that he was climbing out at 220 KTS due to turbulence. The controller told him not to exceed 220 KTS. The flight flew all the way from columbus, oh, to north carolina at 220 KTS. Who first dropped the ball on coordination is unknown. My strip did not show any time updates. That's probably because no one writes them down anymore. ZID is now using 'user requested evaluation tool' and forgotten coordination is a continual problem. Just yesterday, I had several arrs where the speed was not coordination and 1 heading that was not coordination. It is my opinion that 'user requested evaluation tool' is poorly thought out and is contributing to numerous errors of this sort.
Original NASA ASRS Text
Title: ZTL DISCOVERS F100 HAS HAD AN UNCOORD SPD RESTR FROM POINT OF DEP WITHOUT ARTCC INTERFAC COORD.
Narrative: ACR X, AN F100, WAS CLRED TO CROSS THE SHINE INTXN AT 12000 FT AND 250 KTS PER LOA WITH ZTL/CLT. THE PLT ASKED IF HE COULD SPD UP NOW, OR IF I WANTED HIM TO WAIT UNTIL SHINE. IT TURNS OUT THE PLT WAS ASSIGNED 220 KTS COMING OUT OF CMH. THE PLT RELAYED THAT HE WAS ASKED HIS SPD AND REPLIED THAT HE WAS CLBING OUT AT 220 KTS DUE TO TURB. THE CTLR TOLD HIM NOT TO EXCEED 220 KTS. THE FLT FLEW ALL THE WAY FROM COLUMBUS, OH, TO NORTH CAROLINA AT 220 KTS. WHO FIRST DROPPED THE BALL ON COORD IS UNKNOWN. MY STRIP DID NOT SHOW ANY TIME UPDATES. THAT'S PROBABLY BECAUSE NO ONE WRITES THEM DOWN ANYMORE. ZID IS NOW USING 'USER REQUESTED EVALUATION TOOL' AND FORGOTTEN COORD IS A CONTINUAL PROB. JUST YESTERDAY, I HAD SEVERAL ARRS WHERE THE SPD WAS NOT COORD AND 1 HDG THAT WAS NOT COORD. IT IS MY OPINION THAT 'USER REQUESTED EVALUATION TOOL' IS POORLY THOUGHT OUT AND IS CONTRIBUTING TO NUMEROUS ERRORS OF THIS SORT.
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.