37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1561288 |
Time | |
Date | 201807 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | CID.Airport |
State Reference | IA |
Aircraft 1 | |
Make Model Name | PA-23-250 Aztec |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X departed cid after completing practice IFR approach; while working departure radar identification-ed them and asked intentions. Aircraft X wanted to depart cid and fly back to alo IFR; I asked requested altitude and they requested 3;000 feet. I put aircraft X on course to alo and 3;000 feet. Workload increased exponentially due to oshkosh overflights and standard IFR arrivals/ departures. At time of this event easily 10+ on a single scope at a time all requesting different things due to low ceilings and traffic. Aircraft X was enroute to alo which has an MVA of 3;400 feet in his flight path. I noticed his exact flight path led him east of the MVA at 3;400 feet; and by the time he reached about 3 miles from the MVA; I issued a climb to 4;000 feet to keep him at a safe altitude. He went slightly inside the 3 mile mark under MVA altitude but above obstruction altitude; and made the climb past 3;400 feet by the time he was 90 degrees away from the obstruction and flying away from it. No accidents or further developments occurred; higher workload than standard due to oshkosh event traffic funneling in. Nothing to recommend; higher than average workload with several abnormal request led to not seeing the issue before it happened.
Original NASA ASRS Text
Title: CID Controller reported a PA27 entering a higher Minimum Vectoring Altitude.
Narrative: Aircraft X departed CID after completing practice IFR approach; while working departure radar ID-ed them and asked intentions. Aircraft X wanted to depart CID and fly back to ALO IFR; I asked requested altitude and they requested 3;000 feet. I put Aircraft X on course to ALO and 3;000 feet. Workload increased exponentially due to Oshkosh overflights and standard IFR arrivals/ departures. At time of this event easily 10+ on a single scope at a time all requesting different things due to low ceilings and traffic. Aircraft X was enroute to ALO which has an MVA of 3;400 feet in his flight path. I noticed his exact flight path led him east of the MVA at 3;400 feet; and by the time he reached about 3 miles from the MVA; I issued a climb to 4;000 feet to keep him at a safe altitude. He went slightly inside the 3 mile mark under MVA altitude but above obstruction altitude; and made the climb past 3;400 feet by the time he was 90 degrees away from the obstruction and flying away from it. No accidents or further developments occurred; higher workload than standard due to Oshkosh event traffic funneling in. Nothing to recommend; higher than average workload with several abnormal request led to not seeing the issue before it happened.
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.