![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 1757345 | 
| Time | |
| Date | 202008 | 
| Local Time Of Day | 1801-2400 | 
| Place | |
| Locale Reference | MWH.Airport | 
| State Reference | WA | 
| Environment | |
| Flight Conditions | VMC | 
| Light | Daylight | 
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng  | 
| Operating Under FAR Part | Part 91 | 
| Flight Phase | Initial Climb | 
| Route In Use | Vectors | 
| Flight Plan | IFR | 
| Person 1 | |
| Function | Local Supervisor / CIC  | 
| Qualification | Air Traffic Control Fully Certified | 
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 16 | 
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Undershoot Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT  | 
Narrative:
Aircraft X was executing practice IFR approaches. The first approach was ILS 32R [and] the second was gls 14L. I issued climbout instructions: 'on departure; you are cleared to ZZZ via radar vectors; turn right heading 360; climb and maintain four thousand.' the pilot read this back correctly. Once airborne again; the pilot checked in with the correct heading and his current altitude; both of which were correct. I was working controller in charge as well so I was paying more attention to tower than I should have; and I missed the part where he said he was climbing to three thousand; so I vectored him for another approach as normal. I didn't catch his altitude until after I had issued the base turn; when the aircraft was already inside the 4;000 ft. MVA.pay attention to the aircraft I am working during initial call up; then go back and catch back up with the traffic on other positions if necessary. Also check for climb when aircraft are approaching higher mvas rather than trusting [that] the pilot will do as instructed.
Original NASA ASRS Text
Title: Tower Local Controller also working as CIC reported being distracted by CIC duties and not noticing an aircraft report a climb to the wrong altitude that resulted in the aircraft flying below the Minimum Vectoring Altitude.
Narrative: Aircraft X was executing practice IFR approaches. The first approach was ILS 32R [and] the second was GLS 14L. I issued climbout instructions: 'On departure; you are cleared to ZZZ via radar vectors; turn right heading 360; climb and maintain four thousand.' The pilot read this back correctly. Once airborne again; the pilot checked in with the correct heading and his current altitude; both of which were correct. I was working CIC as well so I was paying more attention to Tower than I should have; and I missed the part where he said he was climbing to three thousand; so I vectored him for another approach as normal. I didn't catch his altitude until after I had issued the base turn; when the aircraft was already inside the 4;000 ft. MVA.Pay attention to the aircraft I am working during initial call up; then go back and catch back up with the traffic on other positions if necessary. Also check for climb when aircraft are approaching higher MVAs rather than trusting [that] the pilot will do as instructed.
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.