 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Hcf controller voiced concern when a supervisor typed in a departure altitude without coordinating with the controllers assigned position responsibilities.
| Attributes | |
| ACN | 982175 |
| Time | |
| Date | 201112 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | HCF.TRACON |
| State Reference | HI |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
A B737 was on the ground at ogg. He called ogg tower for an altitude; and then ogg tower called D3; which was combined at R3. The R3 controller at the time (not me) gave an altitude of FL310; since FL330 and FL350 were already issued to other aircraft. Apparently; the B737 was not happy with their altitude; so they called their company; who in turn called the supervisor desk. The supervisor typed in FL350 in the flight plan of the B737; and if this controller did not catch it; would have departed and been given the altitude; even though there was not enough separation between the B737 and his company departing koa with FL350 as his altitude. To add to this problem; a third B737 from the same airline off lih also requested FL350. Recommendation; a supervisor should never type in an altitude at his desk with out checking with the controller. This will cause a major safety event.
Original NASA ASRS Text
Title: HCF Controller voiced concern when a supervisor typed in a departure altitude without coordinating with the controllers assigned position responsibilities.
Narrative: A B737 was on the ground at OGG. He called OGG Tower for an altitude; and then OGG Tower called D3; which was combined at R3. The R3 Controller at the time (not me) gave an altitude of FL310; since FL330 and FL350 were already issued to other aircraft. Apparently; the B737 was not happy with their altitude; so they called their Company; who in turn called the Supervisor desk. The Supervisor typed in FL350 in the flight plan of the B737; and if this Controller did not catch it; would have departed and been given the altitude; even though there was not enough separation between the B737 and his company departing KOA with FL350 as his altitude. To add to this problem; a third B737 from the same airline off LIH also requested FL350. Recommendation; a Supervisor should never type in an altitude at his desk with out checking with the Controller. This will cause a major safety event.
Data retrieved from NASA's ASRS site as of April 2012 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.