37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1449601 |
Time | |
Date | 201705 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PWK.Airport |
State Reference | IL |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citationjet (C525/C526) - CJ I / II / III / IV |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Super King Air 300 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Other Instrument 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 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence |
Narrative:
Chicago executive airport has an instrument approach to only one runway (runway 16). So; when the winds are favoring runway 34; aircraft are asked to cancel their IFR prior to circling because of our proximity to ord airport. If the field is IFR; C90 needs to protect for the circle with O'hare's traffic. When I began working the local control position; winds were gusting out of the northeast at over 20 knots and aircraft were canceling IFR and circling to runway 34 with a ceiling of BKN011. An EA50 reported the cloud bases at 1;500 MSL. Our field elevation is 646 AGL. The one-minute ASOS observation indicated BKN009. The C90 north satellite sector was informed that the field was IFR with a ceiling of BKN009. A speci transmitted indicating 01014g22kt 10SM BKN009.aircraft X called on the RNAV runway 16 approach. He was instructed to circle west for left traffic for runway 34. Aircraft Y called on the RNAV runway 16 approach approximately 6 miles in trail of aircraft X who had just begun his circle. Realizing standard separation would ultimately be lost if the scenario continued; I called C90 to ask for missed approach instructions for aircraft Y. C90 gave me a 040-heading. While issuing the missed approach to aircraft Y; C90 called on the shout line asking if aircraft X failed to cancel his IFR. I reiterated to C90 that the field was IFR and canceling was not an option.when the weather is VFR and aircraft are canceling IFR prior to circling to runway 34; the aircraft either squawk VFR or controllers put the letter 'V' in the special designator area of the data block to signal to C90 that the aircraft is; indeed; now VFR. Neither of those things were happening since I called C90 to inform them of the field being IFR. The standard operating procedures at pwk require controllers to inform C90 when the field goes from VFR to IFR and vice versa. I would recommend that when we are doing this (while advertising the circle to runway 34) that we reiterate to C90; 'field is IFR. You need to protect for the circle to runway 34.' or 'field is VFR. Returning to canceling IFR for the circle to runway 34.'
Original NASA ASRS Text
Title: PWK Controller reported an IFR aircraft that was thought to be VFR due to a procedure usually used in VFR conditions.
Narrative: Chicago Executive Airport has an instrument approach to only one runway (RWY 16). So; when the winds are favoring runway 34; aircraft are asked to cancel their IFR prior to circling because of our proximity to ORD airport. If the field is IFR; C90 needs to protect for the circle with O'Hare's traffic. When I began working the Local Control position; winds were gusting out of the northeast at over 20 knots and aircraft were canceling IFR and circling to runway 34 with a ceiling of BKN011. An EA50 reported the cloud bases at 1;500 MSL. Our field elevation is 646 AGL. The one-minute ASOS observation indicated BKN009. The C90 North Satellite sector was informed that the field was IFR with a ceiling of BKN009. A SPECI transmitted indicating 01014G22KT 10SM BKN009.Aircraft X called on the RNAV RWY 16 approach. He was instructed to circle west for left traffic for runway 34. Aircraft Y called on the RNAV RWY 16 approach approximately 6 miles in trail of Aircraft X who had just begun his circle. Realizing standard separation would ultimately be lost if the scenario continued; I called C90 to ask for missed approach instructions for Aircraft Y. C90 gave me a 040-heading. While issuing the missed approach to Aircraft Y; C90 called on the shout line asking if Aircraft X failed to cancel his IFR. I reiterated to C90 that the field was IFR and canceling was not an option.When the weather is VFR and aircraft are canceling IFR prior to circling to runway 34; the aircraft either squawk VFR or controllers put the letter 'V' in the special designator area of the data block to signal to C90 that the aircraft is; indeed; now VFR. Neither of those things were happening since I called C90 to inform them of the field being IFR. The Standard Operating Procedures at PWK require controllers to inform C90 when the field goes from VFR to IFR and vice versa. I would recommend that when we are doing this (while advertising the circle to runway 34) that we reiterate to C90; 'Field is IFR. You need to protect for the circle to runway 34.' or 'Field is VFR. Returning to canceling IFR for the circle to runway 34.'
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.