37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1376702 |
Time | |
Date | 201607 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Direct |
Flight Plan | VFR |
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 100 Flight Crew Total 8000 Flight Crew Type 20 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 1.5 Vertical 500 |
Narrative:
I departed ajo straight out on a VFR flight in a cessna 310. After 2 miles I turned northwest on course and away from rising terrain. With ontario class C airspace above me and chino class D to the north; I attempted contact with socal approach on 135.4 seeking to climb above 2;500 MSL through both airport's airspace. I called socal approach 3 times unsuccessfully. They were busy and didn't acknowledge any of my calls. My garmin 430 indicated multiple traffic contacts in the vicinity which kept my focus outside. The most pressing contact was at 12 o'clock; westbound within 2 miles and 500 feet. Once I gained visual contact it became apparent that we were converging. The contact appeared to be a cessna high-wing (possibly departing chino) in the climb out at a much lower airspeed. That aircraft had the right-of-way since it was on my right. I elected to turn behind it to avoid closer contact.the turn put me in edge of the southwest sector of chino's class D airspace as I was informed later. Not having any luck raising socal approach on 135.4; I quickly switched to 135.05; the first frequency I found on the sectional chart with a quick glance. I was able to make radio contact with socal on 135.05 on the first or second attempt. Once checked in with a squawk code and was identified; I was issued multiple traffic advisories and limited climbs. Within the first two minutes I was issued 4 different traffic advisories. My course to avoid brackett and el monte class D airspace took me towards the congested practice area; the source of a few of the traffic advisories. During the multiple traffic advisories socal informed me of the possible pilot deviation and requested I copy the number for chino tower. Obviously this was a bad time to be heads-down in the cockpit. I copied the number and eventually read it back. I was eventually approved for a climb out of the low-level area.I contacted chino tower with the number provided and they indicated the information would be forwarded to the local FSDO and I might be contacted for follow-up.I radioed to socal that I had traffic in sight only to be informed of other targets close by. My decision to yield right-of-way took me into the class D airspace and I chose to attempt contact with the TRACON in an effort to climb through class C and D airspace instead of getting stuck hopping from class D tower to tower in low level (class D) congestion. At the time it was more important to keep my head outside instead of inside the airplane looking for class D tower frequencies of chino; brackett; and el monte.my flights to the central valley of california on a northwest course sometimes feel like trying to thread a needle through airspace with ontario's class C above; chino's class D immediately to the north; and los angeles's class B shelves nearby to the west. I'm normally able to get established with TRACON quickly but it was a busy period for the controllers and they didn't have time for me. The focus on avoiding multiple traffic contacts and observing right-of-way rules put me into a tough situation. My attempts at radio contact were initially unsuccessful which caused an airspace violation.
Original NASA ASRS Text
Title: Pilot reported his flight departed out of an airport in a complex and congested airspace environment and inadvertently entered towered airspace without clearance.
Narrative: I departed AJO straight out on a VFR flight in a Cessna 310. After 2 miles I turned northwest on course and away from rising terrain. With Ontario Class C airspace above me and Chino Class D to the north; I attempted contact with SoCal Approach on 135.4 seeking to climb above 2;500 MSL through both airport's airspace. I called SoCal approach 3 times unsuccessfully. They were busy and didn't acknowledge any of my calls. My Garmin 430 indicated multiple traffic contacts in the vicinity which kept my focus outside. The most pressing contact was at 12 o'clock; westbound within 2 miles and 500 feet. Once I gained visual contact it became apparent that we were converging. The contact appeared to be a Cessna high-wing (possibly departing Chino) in the climb out at a much lower airspeed. That aircraft had the right-of-way since it was on my right. I elected to turn behind it to avoid closer contact.The turn put me in edge of the southwest sector of Chino's Class D airspace as I was informed later. Not having any luck raising SoCal Approach on 135.4; I quickly switched to 135.05; the first frequency I found on the Sectional Chart with a quick glance. I was able to make radio contact with SoCal on 135.05 on the first or second attempt. Once checked in with a squawk code and was identified; I was issued multiple traffic advisories and limited climbs. Within the first two minutes I was issued 4 different traffic advisories. My course to avoid Brackett and El Monte Class D airspace took me towards the congested practice area; the source of a few of the traffic advisories. During the multiple traffic advisories SoCal informed me of the possible Pilot Deviation and requested I copy the number for Chino tower. Obviously this was a bad time to be heads-down in the cockpit. I copied the number and eventually read it back. I was eventually approved for a climb out of the low-level area.I contacted Chino tower with the number provided and they indicated the information would be forwarded to the local FSDO and I might be contacted for follow-up.I radioed to SoCal that I had traffic in sight only to be informed of other targets close by. My decision to yield right-of-way took me into the Class D airspace and I chose to attempt contact with the TRACON in an effort to climb through Class C and D airspace instead of getting stuck hopping from Class D tower to tower in low level (Class D) congestion. At the time it was more important to keep my head outside instead of inside the airplane looking for Class D tower frequencies of Chino; Brackett; and El Monte.My flights to the central valley of California on a Northwest course sometimes feel like trying to thread a needle through airspace with Ontario's Class C above; Chino's Class D immediately to the north; and Los Angeles's Class B shelves nearby to the west. I'm normally able to get established with TRACON quickly but it was a busy period for the controllers and they didn't have time for me. The focus on avoiding multiple traffic contacts and observing right-of-way rules put me into a tough situation. My attempts at radio contact were initially unsuccessful which caused an airspace violation.
Data retrieved from NASA's ASRS site 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.