Narrative:

Flying sbound on the east edge of orlando class B airspace, at 2900 ft MSL, we entered controled airspace. At the time we believed we were under the 3000-10000 ft control area. After GPS alarm 'entering control area' we consulted our unofficial 'flight guide' depiction of orlando TCA and realized we had entered a 1600 ft maximum altitude VFR airport traffic area. No other aircraft were in sight. We were not in any radio contact since we had earlier requested jax flight following and were advised 'too busy.' we were greatly concerned at the time, and feel this breach of airspace was caused by the following: inadequate flight planning. Refusal to believe GPS warnings. Failure to consult class B chart. To prevent a recurrence, we will not enter the proximity of class B without consulting a current class B chart. Sectional chart depiction of congested areas, such as this class B, are too difficult to break out the very important details needed for a safe flight. Also, we will heed all GPS alarms, and reverse course to asses the situation before proceeding. After discussing this with other pilots, we would hope for the following improvements: a) better access to flight following in heavy traffic areas -- chicago, atlanta, orlando, ny, dc, etc. B) bolder chart outlines for altitude restr areas. C) VFR corridors where MOA, restr, TCA limits form wide solid walls of impenetrable area, corridors where one can safely traverse the area VFR. Callback conversation with reporter revealed the following information: the reporter stated that he was flying a bonanza, BE35A, from his home town in illinois to florida. So far, no one from the FAA has contacted him regarding his blunder into mco's class B airspace. He provided a number of good suggestions which are noted in his report.

Related reports:

Google
 

Original NASA ASRS Text

Title: A PVT PLT INADVERTENTLY ENTERED MCO CLASS B AIRSPACE AFTER BEING TOLD THAT TRACON WAS UNABLE TO PROVIDE FLT FOLLOWING.

Narrative: FLYING SBOUND ON THE E EDGE OF ORLANDO CLASS B AIRSPACE, AT 2900 FT MSL, WE ENTERED CTLED AIRSPACE. AT THE TIME WE BELIEVED WE WERE UNDER THE 3000-10000 FT CTL AREA. AFTER GPS ALARM 'ENTERING CTL AREA' WE CONSULTED OUR UNOFFICIAL 'FLT GUIDE' DEPICTION OF ORLANDO TCA AND REALIZED WE HAD ENTERED A 1600 FT MAX ALT VFR ARPT TFC AREA. NO OTHER ACFT WERE IN SIGHT. WE WERE NOT IN ANY RADIO CONTACT SINCE WE HAD EARLIER REQUESTED JAX FLT FOLLOWING AND WERE ADVISED 'TOO BUSY.' WE WERE GREATLY CONCERNED AT THE TIME, AND FEEL THIS BREACH OF AIRSPACE WAS CAUSED BY THE FOLLOWING: INADEQUATE FLT PLANNING. REFUSAL TO BELIEVE GPS WARNINGS. FAILURE TO CONSULT CLASS B CHART. TO PREVENT A RECURRENCE, WE WILL NOT ENTER THE PROX OF CLASS B WITHOUT CONSULTING A CURRENT CLASS B CHART. SECTIONAL CHART DEPICTION OF CONGESTED AREAS, SUCH AS THIS CLASS B, ARE TOO DIFFICULT TO BREAK OUT THE VERY IMPORTANT DETAILS NEEDED FOR A SAFE FLT. ALSO, WE WILL HEED ALL GPS ALARMS, AND REVERSE COURSE TO ASSES THE SIT BEFORE PROCEEDING. AFTER DISCUSSING THIS WITH OTHER PLTS, WE WOULD HOPE FOR THE FOLLOWING IMPROVEMENTS: A) BETTER ACCESS TO FLT FOLLOWING IN HVY TFC AREAS -- CHICAGO, ATLANTA, ORLANDO, NY, DC, ETC. B) BOLDER CHART OUTLINES FOR ALT RESTR AREAS. C) VFR CORRIDORS WHERE MOA, RESTR, TCA LIMITS FORM WIDE SOLID WALLS OF IMPENETRABLE AREA, CORRIDORS WHERE ONE CAN SAFELY TRAVERSE THE AREA VFR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT HE WAS FLYING A BONANZA, BE35A, FROM HIS HOME TOWN IN ILLINOIS TO FLORIDA. SO FAR, NO ONE FROM THE FAA HAS CONTACTED HIM REGARDING HIS BLUNDER INTO MCO'S CLASS B AIRSPACE. HE PROVIDED A NUMBER OF GOOD SUGGESTIONS WHICH ARE NOTED IN HIS RPT.

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.