 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Boi clearance delivery controller did not catch an incorrect read back which caused an aircraft to level off in a higher MVA [minimum vectoring altitude]; below the MVA altitude.
| Attributes | |
| ACN | 1595968 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BOI.TRACON |
| State Reference | ID |
| Aircraft 1 | |
| Make Model Name | Super King Air 200 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Undershoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Working clearance delivery. Very slow on thanksgiving. Aircraft X called up for an IFR to sff (felts field; wa). Gave him the IFR clearance with 'fly runway heading; maintain 160.' he read back 'fly runway heading; up to 60.' I totally missed the read back. Tower departed him and changed to departure. Aircraft X reported on with radar climbing to 60; but radar missed the altitude also....he assumed 160 too. Aircraft x told radar they were 'level at 60' in a 6;500 MVA. Supervisor told me about it about an hour later after he reviewed the tapes.talk about expectation bias! I didn't listen completely to his read back. I wasn't preoccupied; and I wasn't busy; just missed the altitude read back. I think the pilots read back of 'fly runway heading; up to 6 thousand' might have sounded a little bit like 'one six thousand' but it's no excuse. I didn't catch the wrong read back and it was a perfect 'swiss cheese' model we've been talking about for the last 15 or more years!more vigilance!less distraction!focus on the pilots' read back and just don't assume it's going to be correct!
Original NASA ASRS Text
Title: BOI Clearance Delivery Controller did not catch an incorrect read back which caused an aircraft to level off in a higher MVA [Minimum Vectoring Altitude]; below the MVA altitude.
Narrative: Working clearance delivery. Very slow on Thanksgiving. Aircraft X called up for an IFR to SFF (Felts Field; WA). Gave him the IFR clearance with 'fly runway heading; maintain 160.' He read back 'fly runway heading; up to 60.' I totally missed the read back. Tower departed him and changed to Departure. Aircraft X reported on with radar climbing to 60; but radar missed the altitude also....he assumed 160 too. Aircraft x told radar they were 'level at 60' in a 6;500 MVA. Supervisor told me about it about an hour later after he reviewed the tapes.Talk about expectation bias! I didn't listen completely to his read back. I wasn't preoccupied; and I wasn't busy; just missed the altitude read back. I think the pilots read back of 'fly runway heading; up to 6 thousand' might have sounded a little bit like 'one six thousand' but it's no excuse. I didn't catch the wrong read back and it was a perfect 'Swiss cheese' model we've been talking about for the last 15 or more years!More vigilance!Less distraction!Focus on the pilots' read back and just don't assume it's going to be correct!
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.