37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1023353 |
Time | |
Date | 201207 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Caravan 208B |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Thunderbolt II (Warthog A-10) |
Operating Under FAR Part | Part 91 |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 2950 Flight Crew Type 820 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Inflight Event / Encounter Weather / Turbulence |
Miss Distance | Vertical 100 |
Narrative:
I picked up an IFR clearance airborne and the controller located the aircraft; which was maintaining VFR; and assigned a southerly heading. I replied that I was unable to comply due to the part 135.183 glide requirement of passenger operations. The controller told me to hold until they could 'work me in' at which time I indicated I had a filed flight plan. I was given clearance to the intersection at 8;000 ft. The controller lost my transponder and then identified me again near the intersection. She vectored me from the intersection on a 240 heading; which took me over the airport and just southeast of the field on what I anticipated were vectors for 04R. I was descended to 6;000. Solid IMC continued. I never obtained a visual on anything within 5 to 10 miles of the airport through breaks in the clouds below. I was switched to the next controller who gave me a 190 heading and assigned me an altitude of 3;000 or below (I can't recall). I determined that this would likely put me in violation of far 135.183; and I advised the controller. He queried why I couldn't comply and I explained the regulation briefly. He told me I should 'get another plane.' he vectored me just offshore at 3;000; which kept me in glide range. The aircraft is supposed to glide 2 NM for every 1;000 ft; in calm wind. At 3;000 ft; I was thus limited to 6 miles from shore. I was vectored in IMC south and at a point approximately five miles off shore; the controller advised that he was going to keep me on that heading for another 2 NM. I contacted the approach controller and advised him that I could not do that and needed to turn in. He said he couldn't turn me in sooner and I stated that I would have to declare an emergency if he didn't. He told me 'go ahead then.' I declared an emergency and gave myself an immediate turn into shore. I was still totally IMC. At this point; the controller identified one or two A-10 warthog military aircraft within three miles of my position. I advised him that I could not see anything and that I was completely IMC. My TAS alerted me to traffic and I saw '-100' immediately near my aircraft on all screens. I think I may have come close to one of these aircraft in the process. I was vectored onto the ILS and eventually broke out of the IMC at around the FAF and landed.
Original NASA ASRS Text
Title: C208 pilot on an IFR flight plan in IMC informs ATC that he cannot be more than two miles off shore for every 1000 feet of altitude; in order to comply with FAR 135.183. With the aircraft being vectored directly off shore and approaching the limit; an emergency is declared and a turn in initiated. This results in a NMAC with a military aircraft.
Narrative: I picked up an IFR clearance airborne and the Controller located the aircraft; which was maintaining VFR; and assigned a southerly heading. I replied that I was unable to comply due to the Part 135.183 glide requirement of passenger operations. The Controller told me to hold until they could 'work me in' at which time I indicated I had a filed flight plan. I was given clearance to the intersection at 8;000 FT. The Controller lost my transponder and then identified me again near the intersection. She vectored me from the intersection on a 240 heading; which took me over the airport and just southeast of the field on what I anticipated were vectors for 04R. I was descended to 6;000. Solid IMC continued. I never obtained a visual on anything within 5 to 10 miles of the airport through breaks in the clouds below. I was switched to the next Controller who gave me a 190 heading and assigned me an altitude of 3;000 or below (I can't recall). I determined that this would likely put me in violation of FAR 135.183; and I advised the Controller. He queried why I couldn't comply and I explained the regulation briefly. He told me I should 'get another plane.' He vectored me just offshore at 3;000; which kept me in glide range. The aircraft is supposed to glide 2 NM for every 1;000 FT; in calm wind. At 3;000 FT; I was thus limited to 6 miles from shore. I was vectored in IMC south and at a point approximately five miles off shore; the Controller advised that he was going to keep me on that heading for another 2 NM. I contacted the Approach Controller and advised him that I could not do that and needed to turn in. He said he couldn't turn me in sooner and I stated that I would have to declare an emergency if he didn't. He told me 'go ahead then.' I declared an emergency and gave myself an immediate turn into shore. I was still totally IMC. At this point; the Controller identified one or two A-10 Warthog military aircraft within three miles of my position. I advised him that I could not see anything and that I was completely IMC. My TAS alerted me to traffic and I saw '-100' immediately near my aircraft on all screens. I think I may have come close to one of these aircraft in the process. I was vectored onto the ILS and eventually broke out of the IMC at around the FAF and landed.
Data retrieved from NASA's ASRS site as of July 2013 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.