37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1409560 |
Time | |
Date | 201612 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TWF.TRACON |
State Reference | ID |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.5 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Aircraft X was coordinated direct maltt for the ILS runway 26 approach; at 12000 and was cleared on the approach. Aircraft Y was released by approach outbound on the twf 020 radial climbing to 12000 reference both aircraft X and aircraft Z who was coordinated direct roget at 13000. Aircraft Z was cleared to the strik outer marker via direct roget; 13 DME arc and the localizer; report roget; no delay expected; but was not issued an altitude to maintain. Aircraft Z used non-standard phraseology to the effect of 'ok here we go.' aircraft Z did not report roget. Aircraft Y was asked DME from twf VORTAC; as he was outbound on the twf 020 radial. 5 DME was the call; and aircraft Z; who was on the localizer was issued holding at strik with an altitude of 13000 to maintain. Aircraft Z read back holding instructions; and asked if he needed to climb back to 13000 from his current altitude of 6000. At this time aircraft X was an arrival; and aircraft Z was vertically clear of aircraft Y. I inquired about the altitude and position; then instructed aircraft Z to contact tower. Tower was given control for ILS clearance; and aircraft Z was cleared on the approach. Aircraft Z was neither issued a descent from 13000 to 6000 nor were they cleared on the approach. Although the brasher warning was not issued; the pilot was instructed to call the tower on ground control frequency. The pilot of aircraft Z advised in the phone conversation that the co-pilot indicated they had been cleared for the approach.use of standard phraseology could have prevented this incident. The phase used by the pilot 'ok; here we go;' as a controller I don't know what that means. Does that mean we will follow the assigned routing to strik outer marker? That is what I thought it meant. I was shocked when aircraft Z reported level at 6000. I admit that I should have assigned an altitude in conjunction with the tentative holding instructions; however; the last assigned altitude was 13000; and absence of an approach clearance should have indicated that they were not cleared on the approach. I will be extra careful to issue an altitude to maintain with any clearance to hold; and when I hear ambiguous phraseology; I will ask questions or restate instructions to verify compliance.
Original NASA ASRS Text
Title: TWF Approach Controller reported an aircraft began their descent without prior clearance due to an apparent communication breakdown.
Narrative: Aircraft X was coordinated direct MALTT for the ILS Runway 26 approach; at 12000 and was cleared on the approach. Aircraft Y was released by approach outbound on the TWF 020 radial climbing to 12000 reference both Aircraft X and Aircraft Z who was coordinated direct ROGET at 13000. Aircraft Z was cleared to the STRIK outer marker via direct ROGET; 13 DME arc and the localizer; report ROGET; no delay expected; but was not issued an altitude to maintain. Aircraft Z used non-standard phraseology to the effect of 'ok here we go.' Aircraft Z did not report ROGET. Aircraft Y was asked DME from TWF VORTAC; as he was outbound on the TWF 020 radial. 5 DME was the call; and Aircraft Z; who was on the localizer was issued holding at STRIK with an altitude of 13000 to maintain. Aircraft Z read back holding instructions; and asked if he needed to climb back to 13000 from his current altitude of 6000. At this time Aircraft X was an arrival; and Aircraft Z was vertically clear of Aircraft Y. I inquired about the altitude and position; then instructed Aircraft Z to contact tower. Tower was given control for ILS clearance; and Aircraft Z was cleared on the approach. Aircraft Z was neither issued a descent from 13000 to 6000 nor were they cleared on the approach. Although the brasher warning was not issued; the pilot was instructed to call the tower on Ground Control frequency. The pilot of Aircraft Z advised in the phone conversation that the co-pilot indicated they had been cleared for the approach.Use of standard phraseology could have prevented this incident. The phase used by the pilot 'ok; here we go;' as a controller I don't know what that means. Does that mean we will follow the assigned routing to STRIK outer marker? That is what I thought it meant. I was shocked when Aircraft Z reported level at 6000. I admit that I should have assigned an altitude in conjunction with the tentative holding instructions; however; the last assigned altitude was 13000; and absence of an approach clearance should have indicated that they were not cleared on the approach. I will be extra careful to issue an altitude to maintain with any clearance to hold; and when I hear ambiguous phraseology; I will ask questions or restate instructions to verify compliance.
Data retrieved from NASA's ASRS site 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.