37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 728599 |
Time | |
Date | 200702 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : fme.airport |
State Reference | MD |
Altitude | msl single value : 1300 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : personal |
Make Model Name | Sierra 24 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | DVR |
Aircraft 2 | |
Make Model Name | Cessna Single Piston Undifferentiated or Other Model |
Flight Phase | climbout : initial |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 25 flight time total : 650 flight time type : 200 |
ASRS Report | 728599 |
Person 2 | |
Function | flight crew : single pilot |
Events | |
Anomaly | airspace violation : entry altitude deviation : excursion from assigned altitude conflict : airborne critical non adherence : clearance non adherence : far |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued alert flight crew : returned to assigned airspace flight crew : returned to assigned altitude |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance Airspace Structure |
Primary Problem | Flight Crew Human Performance |
Narrative:
I was flying to jyo to drop passenger and then fly to ZZZ. I filed an ADIZ flight plan; entered at golda and was advised to stay below class B airspace. Compressed into the airspace below 1500 ft and wanting to stay as high as possible to avoid the towers that are littered in that corridor and stay well away from the frz; I was cruising along at about 1400 ft when advised that I was in the class B. I descended to 1300 ft and that seemed to take care of it. The controller reported that my altitude was within allowable error. I was approaching tipton from the east at 1300 ft when a cessna took off from runway 28. I maintained a parallel course to the runway so as to not intersect his path and my cruise airspeed combined with his climb out airspeed indicated that I would pass him reasonably far off his left wing and that I would overtake him quickly. Tipton is only 150 ft in elevation; so he should have been nearly 200 ft below me at best if he was staying in the pattern. Past the departure end; the cessna turned toward; continued to climb and passed pretty close behind my airplane. The gap closed very fast. After the cessna passed behind; the controller tried calling me to give me an alert; but; when he saw that the cessna was no longer a factor; went on to some other airplane without completing the transmission. I called him back later when he didn't seem so busy and he let me know he was about to tell me about the plane I had seen. Nearly the same thing happened shortly afterward over gaithersburg with a plane working the pattern there. The difference there being that I could have climbed in that airspace...only to have to come back down a few mins later to approach jyo. Contributing factors: 1) compressed airspace. The lateral distance between the class B surface area and the frz isn't very far. Tipton is in the middle of it. The vertical dimensions of the airspace are poor as well. A 1500 ft ceiling amidst towers puts transiting traffic right at pattern altitude. 2) poor ATC structure and overload. The controller controling my airplane was obviously not working approachs and departures. It appeared that he was only working ADIZ traffic. He was not clearing anyone into class B airspace to make efficient use of it and avoid conflict. It appeared to me that the frequency and controller were dedicated to ADIZ traffic and he would have to hand me off to another controller in the class B. Given his workload; it appeared that he would not have been able to do this. It also appears that the system is designed to reduce workload on approach/departure controllers and not to make efficient use of the airspace. 3) communication. If the cessna entered the airspace legally; he would have had to talk to clearance delivery to receive his squawk. If clearance delivery looked at the radar or talked to the controller working me; the potential for conflict would have been seen and a hold for release instruction could have been issued to the cessna. That didn't appear to have happened. 4) frequency congestion. I saw this situation developing while the cessna was still on the ground. I couldn't advise that I was turning toward the frz to avoid the traffic; or advise that I needed a climb temporarily to avoid the traffic. Future considerations: 1) I am an IFR pilot. I will not fly VFR under the class B ring as I don't believe it is safe or well controled. The structure of the airspace itself compresses traffic very close to towers and has limited lateral boundaries. 2) I discounted my thoughts of deviating to the south toward the frz unannounced because I didn't want to alarm anyone watching the radar. I discounted my thoughts of climbing unannounced due to the class B. Next time; I will not allow the situation to play out. I will utilize my PIC authority/authorized; squawk 7700; and deviate. Note: I researched this problem at tipton using the ASRS website. It's happened before. High wing aircraft have trouble seeing traffic cruising in that area.
Original NASA ASRS Text
Title: BE24 PLT HAS NMAC IN DCA ADIZ BELOW CLASS B AIRSPACE.
Narrative: I WAS FLYING TO JYO TO DROP PAX AND THEN FLY TO ZZZ. I FILED AN ADIZ FLT PLAN; ENTERED AT GOLDA AND WAS ADVISED TO STAY BELOW CLASS B AIRSPACE. COMPRESSED INTO THE AIRSPACE BELOW 1500 FT AND WANTING TO STAY AS HIGH AS POSSIBLE TO AVOID THE TWRS THAT ARE LITTERED IN THAT CORRIDOR AND STAY WELL AWAY FROM THE FRZ; I WAS CRUISING ALONG AT ABOUT 1400 FT WHEN ADVISED THAT I WAS IN THE CLASS B. I DSNDED TO 1300 FT AND THAT SEEMED TO TAKE CARE OF IT. THE CTLR RPTED THAT MY ALT WAS WITHIN ALLOWABLE ERROR. I WAS APCHING TIPTON FROM THE E AT 1300 FT WHEN A CESSNA TOOK OFF FROM RWY 28. I MAINTAINED A PARALLEL COURSE TO THE RWY SO AS TO NOT INTERSECT HIS PATH AND MY CRUISE AIRSPD COMBINED WITH HIS CLBOUT AIRSPD INDICATED THAT I WOULD PASS HIM REASONABLY FAR OFF HIS L WING AND THAT I WOULD OVERTAKE HIM QUICKLY. TIPTON IS ONLY 150 FT IN ELEVATION; SO HE SHOULD HAVE BEEN NEARLY 200 FT BELOW ME AT BEST IF HE WAS STAYING IN THE PATTERN. PAST THE DEP END; THE CESSNA TURNED TOWARD; CONTINUED TO CLB AND PASSED PRETTY CLOSE BEHIND MY AIRPLANE. THE GAP CLOSED VERY FAST. AFTER THE CESSNA PASSED BEHIND; THE CTLR TRIED CALLING ME TO GIVE ME AN ALERT; BUT; WHEN HE SAW THAT THE CESSNA WAS NO LONGER A FACTOR; WENT ON TO SOME OTHER AIRPLANE WITHOUT COMPLETING THE XMISSION. I CALLED HIM BACK LATER WHEN HE DIDN'T SEEM SO BUSY AND HE LET ME KNOW HE WAS ABOUT TO TELL ME ABOUT THE PLANE I HAD SEEN. NEARLY THE SAME THING HAPPENED SHORTLY AFTERWARD OVER GAITHERSBURG WITH A PLANE WORKING THE PATTERN THERE. THE DIFFERENCE THERE BEING THAT I COULD HAVE CLBED IN THAT AIRSPACE...ONLY TO HAVE TO COME BACK DOWN A FEW MINS LATER TO APCH JYO. CONTRIBUTING FACTORS: 1) COMPRESSED AIRSPACE. THE LATERAL DISTANCE BTWN THE CLASS B SURFACE AREA AND THE FRZ ISN'T VERY FAR. TIPTON IS IN THE MIDDLE OF IT. THE VERT DIMENSIONS OF THE AIRSPACE ARE POOR AS WELL. A 1500 FT CEILING AMIDST TWRS PUTS TRANSITING TFC RIGHT AT PATTERN ALT. 2) POOR ATC STRUCTURE AND OVERLOAD. THE CTLR CTLING MY AIRPLANE WAS OBVIOUSLY NOT WORKING APCHS AND DEPS. IT APPEARED THAT HE WAS ONLY WORKING ADIZ TFC. HE WAS NOT CLRING ANYONE INTO CLASS B AIRSPACE TO MAKE EFFICIENT USE OF IT AND AVOID CONFLICT. IT APPEARED TO ME THAT THE FREQ AND CTLR WERE DEDICATED TO ADIZ TFC AND HE WOULD HAVE TO HAND ME OFF TO ANOTHER CTLR IN THE CLASS B. GIVEN HIS WORKLOAD; IT APPEARED THAT HE WOULD NOT HAVE BEEN ABLE TO DO THIS. IT ALSO APPEARS THAT THE SYS IS DESIGNED TO REDUCE WORKLOAD ON APCH/DEP CTLRS AND NOT TO MAKE EFFICIENT USE OF THE AIRSPACE. 3) COM. IF THE CESSNA ENTERED THE AIRSPACE LEGALLY; HE WOULD HAVE HAD TO TALK TO CLRNC DELIVERY TO RECEIVE HIS SQUAWK. IF CLRNC DELIVERY LOOKED AT THE RADAR OR TALKED TO THE CTLR WORKING ME; THE POTENTIAL FOR CONFLICT WOULD HAVE BEEN SEEN AND A HOLD FOR RELEASE INSTRUCTION COULD HAVE BEEN ISSUED TO THE CESSNA. THAT DIDN'T APPEAR TO HAVE HAPPENED. 4) FREQ CONGESTION. I SAW THIS SITUATION DEVELOPING WHILE THE CESSNA WAS STILL ON THE GND. I COULDN'T ADVISE THAT I WAS TURNING TOWARD THE FRZ TO AVOID THE TFC; OR ADVISE THAT I NEEDED A CLB TEMPORARILY TO AVOID THE TFC. FUTURE CONSIDERATIONS: 1) I AM AN IFR PLT. I WILL NOT FLY VFR UNDER THE CLASS B RING AS I DON'T BELIEVE IT IS SAFE OR WELL CTLED. THE STRUCTURE OF THE AIRSPACE ITSELF COMPRESSES TFC VERY CLOSE TO TWRS AND HAS LIMITED LATERAL BOUNDARIES. 2) I DISCOUNTED MY THOUGHTS OF DEVIATING TO THE S TOWARD THE FRZ UNANNOUNCED BECAUSE I DIDN'T WANT TO ALARM ANYONE WATCHING THE RADAR. I DISCOUNTED MY THOUGHTS OF CLBING UNANNOUNCED DUE TO THE CLASS B. NEXT TIME; I WILL NOT ALLOW THE SITUATION TO PLAY OUT. I WILL UTILIZE MY PIC AUTH; SQUAWK 7700; AND DEVIATE. NOTE: I RESEARCHED THIS PROB AT TIPTON USING THE ASRS WEBSITE. IT'S HAPPENED BEFORE. HIGH WING ACFT HAVE TROUBLE SEEING TFC CRUISING IN THAT AREA.
Data retrieved from NASA's ASRS site as of January 2009 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.