37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 106941 |
Time | |
Date | 198903 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : zid |
State Reference | IN |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 5 |
ASRS Report | 106941 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
Reference 'call back #117,' 3/89. In your first paragraph the pilot is talking about missing a crossing altitude. Your response is, 'bad attitude,' and possible 'deal for controller!' I issuing crossing restrictions for 2 reasons: 1) it allows the pilot to fly his own plane. He can descend his plane as soon or as late as he wants, as long as the crossing is met. 2) or traffic, to meet an agreement with approach control, or to clear an aircraft from a corridor. If I give a pilot a crossing and a sep error occurs because he was too high, then this is not a deal, it would be a 'pilot deviation.' if the pilot notifies that he can't make the crossing in enough time that I can save sep, only then is the burden back on the controller. Another point and maybe bad procedure is that if I have given a crossing for traffic, then a lot of times I don't pay as much attention to that situation because I believe it's taken care of.
Original NASA ASRS Text
Title: REPORTER DOES NOT AGREE WITH 'CALLBACK #117' COMMENTS CONCERNING CROSSING RESTRICTIONS.
Narrative: REF 'CALL BACK #117,' 3/89. IN YOUR FIRST PARAGRAPH THE PLT IS TALKING ABOUT MISSING A XING ALT. YOUR RESPONSE IS, 'BAD ATTITUDE,' AND POSSIBLE 'DEAL FOR CTLR!' I ISSUING XING RESTRICTIONS FOR 2 REASONS: 1) IT ALLOWS THE PLT TO FLY HIS OWN PLANE. HE CAN DSND HIS PLANE AS SOON OR AS LATE AS HE WANTS, AS LONG AS THE XING IS MET. 2) OR TFC, TO MEET AN AGREEMENT WITH APCH CTL, OR TO CLR AN ACFT FROM A CORRIDOR. IF I GIVE A PLT A XING AND A SEP ERROR OCCURS BECAUSE HE WAS TOO HIGH, THEN THIS IS NOT A DEAL, IT WOULD BE A 'PLTDEV.' IF THE PLT NOTIFIES THAT HE CAN'T MAKE THE XING IN ENOUGH TIME THAT I CAN SAVE SEP, ONLY THEN IS THE BURDEN BACK ON THE CTLR. ANOTHER POINT AND MAYBE BAD PROC IS THAT IF I HAVE GIVEN A XING FOR TFC, THEN A LOT OF TIMES I DON'T PAY AS MUCH ATTN TO THAT SITUATION BECAUSE I BELIEVE IT'S TAKEN CARE OF.
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.