37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 529502 |
Time | |
Date | 200111 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : bkl.airport |
State Reference | OH |
Altitude | msl single value : 3000 |
Environment | |
Flight Conditions | Mixed |
Aircraft 1 | |
Controlling Facilities | tracon : cle.tracon |
Operator | general aviation : instructional |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Navigation In Use | ils localizer & glide slope : 24r |
Flight Phase | descent : approach |
Route In Use | approach : instrument precision |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot instruction : instructor oversight : pic |
Qualification | pilot : multi engine pilot : cfi pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 140 flight time total : 600 flight time type : 500 |
ASRS Report | 529502 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot instruction : trainee |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 25 flight time total : 121 flight time type : 121 |
ASRS Report | 529501 |
Events | |
Anomaly | inflight encounter : weather inflight encounter other non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Weather Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We contacted cle approach on 125.35 over cxr VOR for an ILS runway 24R approach into burke lakefront airport. We were then given a transponder code and vectors for the ILS runway 24R. When on the final approach course, ATC advised us of traffic and we replied that we were in a cloud. Cle approach then advised us that we were supposed to be VFR. The other pilot and myself were under the understanding that we had been under IFR. I am still unsure if the controller initially stated to maintain VFR. I have learned that in the future I will make my requests clrer so there is no misunderstanding whether I am VFR or IFR. If ever in doubt I will query ATC. In the future, I will use the words 'IFR clearance' to clarify the request, or file a composite flight plan that states IFR or VFR, and which parts of the flight are VFR versus IFR. Supplemental information from acn 529501: we were under the impression we were being vectored IFR. Neither myself nor my safety pilot recall approach control advising us to 'maintain VFR.'
Original NASA ASRS Text
Title: A VFR C172 TRAINING FLT GOES IMC IN VFR FLT DURING A REQUESTED VECTOR FOR AN ILS RWY 24R AT BKL, OH.
Narrative: WE CONTACTED CLE APCH ON 125.35 OVER CXR VOR FOR AN ILS RWY 24R APCH INTO BURKE LAKEFRONT ARPT. WE WERE THEN GIVEN A XPONDER CODE AND VECTORS FOR THE ILS RWY 24R. WHEN ON THE FINAL APCH COURSE, ATC ADVISED US OF TFC AND WE REPLIED THAT WE WERE IN A CLOUD. CLE APCH THEN ADVISED US THAT WE WERE SUPPOSED TO BE VFR. THE OTHER PLT AND MYSELF WERE UNDER THE UNDERSTANDING THAT WE HAD BEEN UNDER IFR. I AM STILL UNSURE IF THE CTLR INITIALLY STATED TO MAINTAIN VFR. I HAVE LEARNED THAT IN THE FUTURE I WILL MAKE MY REQUESTS CLRER SO THERE IS NO MISUNDERSTANDING WHETHER I AM VFR OR IFR. IF EVER IN DOUBT I WILL QUERY ATC. IN THE FUTURE, I WILL USE THE WORDS 'IFR CLRNC' TO CLARIFY THE REQUEST, OR FILE A COMPOSITE FLT PLAN THAT STATES IFR OR VFR, AND WHICH PARTS OF THE FLT ARE VFR VERSUS IFR. SUPPLEMENTAL INFO FROM ACN 529501: WE WERE UNDER THE IMPRESSION WE WERE BEING VECTORED IFR. NEITHER MYSELF NOR MY SAFETY PLT RECALL APCH CTL ADVISING US TO 'MAINTAIN VFR.'
Data retrieved from NASA's ASRS site as of July 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.