37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 322136 |
Time | |
Date | 199511 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : gai |
State Reference | VA |
Altitude | msl bound lower : 6000 msl bound upper : 7500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : iad |
Operator | general aviation : personal |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 13 flight time total : 7100 flight time type : 35 |
ASRS Report | 322136 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly other |
Independent Detector | other other : unspecified cockpit |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : reviewed incident with flight crew faa : assigned or threatened penalties |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Narrative:
On nov/xa/95, I began a VFR cross country flight from bay bridge airport (W29), md, to kokomo municipal airport (okk), in. The plan was to fly via the VFR corridor (flyway) between the baltimore and washington traffic areas, then proceed direct to martinsburg (mrb) VOR and continue en route. After several attempts to contact leesburg FSS, I was finally successful and activated the flight plan north of freeway airport (W00). I remained at 1500 ft until north of college park airport (cgs), then began a climb to just below 2500 ft (the class B floor at that point). The flight conditions were quite hazy, estimated 3-4 mi visibility (less than forecast). Soon after leveling off, the engine began running very roughly. The nearest airport was montgomery county (gai) approximately 7 NM ahead, however, there was also a layer of clouds ahead that appeared to extend to about 5000 ft. The haze prevented any estimate of the ceiling below. I started to turn back but the visibility to the east was very poor and I could not see the ground (looking toward the morning sun made it worse). So I elected to continue climbing, in the direction of gai in order to maintain VMC, have better gliding range, try to resolve the engine problem, and obtain assistance from approach control. I attempted to contact bwi approach on 2 frequencys, which were very congested, with no success, then tried to call leesburg FSS for assistance. After the third or fourth try I made contact, informed them of my engine problem, and asked for any other appropriate control frequency. Leesburg gave me 2 frequencys for ZDC. Again, I could hear other calls but received no response (attempted both frequencys on both radios). I changed back to FSS, asked for additional frequencys, and was given two for dulles approach. While attempting to make radio contact with a controling agency and trying to diagnose the engine problem, I had climbed to 6500 ft still heading northwest, and was then VMC over an undercast which appeared to extend to the gai airport area. When I continued having trouble making contact, I turned back east toward an area where I could see the ground again (barely), since I did not want to descend through the undercast if the engine failed, especially not knowing the WX conditions at gai. Now at 7500 ft (headed east), I finally contacted dulles. After explaining my situation, I was informed that I was well within class B airspace. Since I had been more concerned about determining the engine status, maintaining VMC, and trying to contact a suitable controling agency, I was not sure of my exact position at that time. I had obviously flown into the northwestern class B area (above 3500 ft) while climbing toward gai (again, to maintain VMC and have more altitude for glide range while attempting radio contact and troubleshooting the engine). Dulles handed me off to bwi approach for flight following and vectors. I was also told to contact dulles approach by phone after landing. I did so and was told that I had been tracked (by transponder) inside class B airspace without clearance and that a deviation report would be filed.
Original NASA ASRS Text
Title: THE RPTR HAD VHF RECEPTION DIFFICULTY. THE RPTR HAD LESS THAN FORECAST VISIBILITY -- A MARGINAL 3-4 MI. THE RPTR'S ENG BEGAN RUNNING VERY ROUGH. TO AVOID CLOUDS AND LOW VISIBILITY AND TO HAVE GLIDING OPTIONS IF THE ROUGH RUNNING ENG SHOULD FAIL THE RPTR CLBED INTO THE CLASS B AIRSPACE WITHOUT BEING ABLE TO ESTABLISH TRACON VHF COM.
Narrative: ON NOV/XA/95, I BEGAN A VFR XCOUNTRY FLT FROM BAY BRIDGE ARPT (W29), MD, TO KOKOMO MUNICIPAL ARPT (OKK), IN. THE PLAN WAS TO FLY VIA THE VFR CORRIDOR (FLYWAY) BTWN THE BALTIMORE AND WASHINGTON TFC AREAS, THEN PROCEED DIRECT TO MARTINSBURG (MRB) VOR AND CONTINUE ENRTE. AFTER SEVERAL ATTEMPTS TO CONTACT LEESBURG FSS, I WAS FINALLY SUCCESSFUL AND ACTIVATED THE FLT PLAN N OF FREEWAY ARPT (W00). I REMAINED AT 1500 FT UNTIL N OF COLLEGE PARK ARPT (CGS), THEN BEGAN A CLB TO JUST BELOW 2500 FT (THE CLASS B FLOOR AT THAT POINT). THE FLT CONDITIONS WERE QUITE HAZY, ESTIMATED 3-4 MI VISIBILITY (LESS THAN FORECAST). SOON AFTER LEVELING OFF, THE ENG BEGAN RUNNING VERY ROUGHLY. THE NEAREST ARPT WAS MONTGOMERY COUNTY (GAI) APPROX 7 NM AHEAD, HOWEVER, THERE WAS ALSO A LAYER OF CLOUDS AHEAD THAT APPEARED TO EXTEND TO ABOUT 5000 FT. THE HAZE PREVENTED ANY ESTIMATE OF THE CEILING BELOW. I STARTED TO TURN BACK BUT THE VISIBILITY TO THE E WAS VERY POOR AND I COULD NOT SEE THE GND (LOOKING TOWARD THE MORNING SUN MADE IT WORSE). SO I ELECTED TO CONTINUE CLBING, IN THE DIRECTION OF GAI IN ORDER TO MAINTAIN VMC, HAVE BETTER GLIDING RANGE, TRY TO RESOLVE THE ENG PROB, AND OBTAIN ASSISTANCE FROM APCH CTL. I ATTEMPTED TO CONTACT BWI APCH ON 2 FREQS, WHICH WERE VERY CONGESTED, WITH NO SUCCESS, THEN TRIED TO CALL LEESBURG FSS FOR ASSISTANCE. AFTER THE THIRD OR FOURTH TRY I MADE CONTACT, INFORMED THEM OF MY ENG PROB, AND ASKED FOR ANY OTHER APPROPRIATE CTL FREQ. LEESBURG GAVE ME 2 FREQS FOR ZDC. AGAIN, I COULD HEAR OTHER CALLS BUT RECEIVED NO RESPONSE (ATTEMPTED BOTH FREQS ON BOTH RADIOS). I CHANGED BACK TO FSS, ASKED FOR ADDITIONAL FREQS, AND WAS GIVEN TWO FOR DULLES APCH. WHILE ATTEMPTING TO MAKE RADIO CONTACT WITH A CTLING AGENCY AND TRYING TO DIAGNOSE THE ENG PROB, I HAD CLBED TO 6500 FT STILL HDG NW, AND WAS THEN VMC OVER AN UNDERCAST WHICH APPEARED TO EXTEND TO THE GAI ARPT AREA. WHEN I CONTINUED HAVING TROUBLE MAKING CONTACT, I TURNED BACK E TOWARD AN AREA WHERE I COULD SEE THE GND AGAIN (BARELY), SINCE I DID NOT WANT TO DSND THROUGH THE UNDERCAST IF THE ENG FAILED, ESPECIALLY NOT KNOWING THE WX CONDITIONS AT GAI. NOW AT 7500 FT (HEADED E), I FINALLY CONTACTED DULLES. AFTER EXPLAINING MY SIT, I WAS INFORMED THAT I WAS WELL WITHIN CLASS B AIRSPACE. SINCE I HAD BEEN MORE CONCERNED ABOUT DETERMINING THE ENG STATUS, MAINTAINING VMC, AND TRYING TO CONTACT A SUITABLE CTLING AGENCY, I WAS NOT SURE OF MY EXACT POS AT THAT TIME. I HAD OBVIOUSLY FLOWN INTO THE NORTHWESTERN CLASS B AREA (ABOVE 3500 FT) WHILE CLBING TOWARD GAI (AGAIN, TO MAINTAIN VMC AND HAVE MORE ALT FOR GLIDE RANGE WHILE ATTEMPTING RADIO CONTACT AND TROUBLESHOOTING THE ENG). DULLES HANDED ME OFF TO BWI APCH FOR FLT FOLLOWING AND VECTORS. I WAS ALSO TOLD TO CONTACT DULLES APCH BY PHONE AFTER LNDG. I DID SO AND WAS TOLD THAT I HAD BEEN TRACKED (BY XPONDER) INSIDE CLASS B AIRSPACE WITHOUT CLRNC AND THAT A DEV RPT WOULD BE FILED.
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.