37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1395486 |
Time | |
Date | 201610 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MDW.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2.8 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was on an IFR flight plan inbound to mdw. C90 started flashing him to me. I didn't take the handoff since aircraft X was IFR (so I thought based on aircraft X's in bound strip) and was flying against the downwind for the 22L approach. C90 never called to coordinate or advise me of their plan. Since I didn't take the handoff aircraft X was then put 5 miles east of mdw outside of the class C going northbound flying under the final for runway 22L where aircraft descend to 2;400. I saw aircraft X's tag disappear and go to 1;200. Aircraft X then called me at VFR at 1;800 right under the 22L final requesting to land. No coordination was ever done by C90.it is my opinion that C90 didn't want to sequence an IFR aircraft in to mdw so C90 decided that they would cancel aircraft X's IFR and mdw tower will work it out for them. This I am sure is not the first time this has happened. This is a complete unsafe situation and should have never happened.having talks with C90 has not done any good over the past few years when stuff like this continues to happen. I think that an outside investigation into how C90 operates need to be done.C90 continues to give everyone lip service about how they are improving and I haven't seen it.is it going to take a horrific accident for things to change?mdw ATCT should never sequence aircraft VFR or IFR to mdw this should be done by the TRACON.
Original NASA ASRS Text
Title: MDW Tower Controller reported an unsafe situation where the overlying TRACON terminated IFR services with an aircraft and transferred communications to the Tower without any coordination. Reporter thought this was not a good practice because of the position of the aircraft related to final.
Narrative: Aircraft X was on an IFR flight plan inbound to MDW. C90 started flashing him to me. I didn't take the handoff since aircraft X was IFR (so I thought based on aircraft X's in bound strip) and was flying against the downwind for the 22L approach. C90 never called to coordinate or advise me of their plan. Since I didn't take the handoff aircraft X was then put 5 miles east of MDW outside of the class C going northbound flying under the final for Runway 22L where aircraft descend to 2;400. I saw Aircraft X's tag disappear and go to 1;200. Aircraft X then called me at VFR at 1;800 right under the 22L final requesting to land. No coordination was ever done by C90.It is my opinion that C90 didn't want to sequence an IFR aircraft in to MDW so C90 decided that they would cancel aircraft X's IFR and MDW Tower will work it out for them. This I am sure is not the first time this has happened. This is a complete unsafe situation and should have never happened.Having talks with C90 has not done any good over the past few years when stuff like this continues to happen. I think that an outside investigation into how C90 operates need to be done.C90 continues to give everyone lip service about how they are improving and I haven't seen it.Is it going to take a horrific accident for things to change?MDW ATCT should never sequence aircraft VFR or IFR to MDW this should be done by the TRACON.
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.