37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 118605 |
Time | |
Date | 198907 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : enw |
State Reference | WI |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mke tower : osh |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | descent : approach |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot instruction : trainee |
Qualification | pilot : instrument pilot : atp |
Experience | flight time last 90 days : 35 flight time total : 3770 flight time type : 2500 |
ASRS Report | 118605 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | other anomaly other |
Independent Detector | other other : unspecified cockpit |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
About 4 months ago, I flew to kenosha, wi, 10 mi from where my aircraft is based (racine, wi) to pick up my safety pilot for instrument work. WX was VFR, but appeared marginal on the flight with the possibility of IFR at vectoring altitudes. Rather than get out of the plane and talk with green bay flight service, my safety pilot said approach control (mke) had been issuing local IFR clrncs on their remote frequency in kenosha. We called, received IFR clearance and flew the practice session. The same situation occurred in july 1989. Clearance was issued as requested. Immediately after being given the final intercept vector for the ILS runway 4 approach to racine, frequency change information, missed approach clearance, etc, the controller said something about green bay FSS wanting additional information. It was unclear whether additional information was to be given the controller, whether I was to contact green bay immediately (which made no sense) contact them later while in the air or on the ground. The last question I asked re clarification went unanswered. We flew that approach and 3 more with no further comment from the controller.
Original NASA ASRS Text
Title: MKE APCH CTLR ADVISED TRAINING FLT TO CONTACT GREEN BAY FSS. PLT TRAINEE DID NOT UNDERSTAND MESSAGE. REQUEST FOR CLARIFICATION WENT UNANSWERED.
Narrative: ABOUT 4 MONTHS AGO, I FLEW TO KENOSHA, WI, 10 MI FROM WHERE MY ACFT IS BASED (RACINE, WI) TO PICK UP MY SAFETY PLT FOR INSTRUMENT WORK. WX WAS VFR, BUT APPEARED MARGINAL ON THE FLT WITH THE POSSIBILITY OF IFR AT VECTORING ALTS. RATHER THAN GET OUT OF THE PLANE AND TALK WITH GREEN BAY FLT SERVICE, MY SAFETY PLT SAID APCH CTL (MKE) HAD BEEN ISSUING LOCAL IFR CLRNCS ON THEIR REMOTE FREQ IN KENOSHA. WE CALLED, RECEIVED IFR CLRNC AND FLEW THE PRACTICE SESSION. THE SAME SITUATION OCCURRED IN JULY 1989. CLRNC WAS ISSUED AS REQUESTED. IMMEDIATELY AFTER BEING GIVEN THE FINAL INTERCEPT VECTOR FOR THE ILS RWY 4 APCH TO RACINE, FREQ CHANGE INFO, MISSED APCH CLRNC, ETC, THE CTLR SAID SOMETHING ABOUT GREEN BAY FSS WANTING ADDITIONAL INFO. IT WAS UNCLEAR WHETHER ADDITIONAL INFO WAS TO BE GIVEN THE CTLR, WHETHER I WAS TO CONTACT GREEN BAY IMMEDIATELY (WHICH MADE NO SENSE) CONTACT THEM LATER WHILE IN THE AIR OR ON THE GND. THE LAST QUESTION I ASKED RE CLARIFICATION WENT UNANSWERED. WE FLEW THAT APCH AND 3 MORE WITH NO FURTHER COMMENT FROM THE CTLR.
Data retrieved from NASA's ASRS site as of August 2007 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.