37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1252886 |
Time | |
Date | 201504 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | C90.TRACON |
State Reference | IL |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Flight Phase | Other holding |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Instructor |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Other / Unknown Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was training on sector 1. Aircraft was cleared for the RNAV runway 30 approach at gyy. Aircraft went missed and asked to hold while they waited for the weather to improve. Certified professional controller-in training (cpc-it) elected to vector the aircraft over lake michigan due to the complexity of the session (ZAU refusing handoffs on mdw departures; multiple missed approaches at mdw) and no suitable place to hold. I concurred with his decision.cpc-it instructed aircraft X to turn to the east; and there was no response. He tried again; and again no response. I took over the sector due to complexity and continued vectoring aircraft into mdw while attempting to contact aircraft X on my frequency and 121.5. I also asked gyy airport traffic control tower (ATCT) and sbn approach to reach out and issue an immediate turn to a heading of 090.aircraft X entered a 3;300 feet MVA at 3;000 feet; almost directly over the hancock building over downtown chicago. Aircraft also passed inside of ord ATCT airspace. Communication was restored as the aircraft passed over pwk.we should have avoided issuing a heading that pointed at a higher MVA and ord airport; even if the aircraft was 20 miles away at the time. A 360 heading would have kept the aircraft over lake michigan and the aircraft would have simply flown toward wisconsin and lower MVA's. We used a 320 heading with the intention of turning away from ord and the higher MVA (which was attempted more than 20 times); which resulted in the NORDO aircraft violating the MVA.
Original NASA ASRS Text
Title: C90 instructor reports of an aircraft that is NORDO and enters a MVA that is higher then the aircrafts altitude; also this aircraft violated Class B and C airspace.
Narrative: I was training on Sector 1. Aircraft was cleared for the RNAV Runway 30 approach at GYY. Aircraft went missed and asked to hold while they waited for the weather to improve. Certified Professional Controller-In Training (CPC-IT) elected to vector the aircraft over Lake Michigan due to the complexity of the session (ZAU refusing handoffs on MDW departures; multiple missed approaches at MDW) and no suitable place to hold. I concurred with his decision.CPC-IT instructed Aircraft X to turn to the east; and there was no response. He tried again; and again no response. I took over the sector due to complexity and continued vectoring aircraft into MDW while attempting to contact Aircraft X on my frequency and 121.5. I also asked GYY Airport Traffic Control Tower (ATCT) and SBN Approach to reach out and issue an immediate turn to a heading of 090.Aircraft X entered a 3;300 feet MVA at 3;000 feet; almost directly over the Hancock building over downtown Chicago. Aircraft also passed inside of ORD ATCT airspace. Communication was restored as the aircraft passed over PWK.We should have avoided issuing a heading that pointed at a higher MVA and ORD airport; even if the aircraft was 20 miles away at the time. A 360 heading would have kept the aircraft over Lake Michigan and the aircraft would have simply flown toward Wisconsin and lower MVA's. We used a 320 heading with the intention of turning away from ORD and the higher MVA (which was attempted more than 20 times); which resulted in the NORDO aircraft violating the MVA.
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.