<< >> NASA ASRS Report 417690, October 1998

An AC14 pilot experiences an unauthorized penetration of airspace, the class D of myf after a no handoff from san approach.

Attributes
ACN	417690
Time
Date	199810
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mzb airport : myf
State Reference	CA
Altitude	msl bound lower : 2500 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : san
Operator	general aviation : personal
Make Model Name	Commander 114
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 40 flight time total : 900 flight time type : 350
ASRS Report	417690
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : far non adherence : published procedure other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

VFR flight to myf via V23. Flight following provided by socal approach. My plan was to proceed to mission bay VOR at 2500 ft then direct to myf. Controller requested that I turn direct to myf about 2 mi prior to VOR. I complied. Flight following was canceled and I was told to contact myf tower. By the time I contacted myf tower, I was in their class D airspace. Tower controller told me to not enter class D without their approval (which is correct). Factors: 1) socal controller was very busy separating high speed military traffic and other aircraft, VFR and IFR. 2) airspace was very congested with IFR/VFR aircraft. 3) myf was reporting 2500 ft scattered, 3000 ft broken. 4) it was difficult to raise myf due to frequency congestion. 5) I had no idea that handoffs were not made between approach and tower as at some other facilities for VFR aircraft (oakland, monterey, reno, palm springs). 5) it is extremely dangerous to just wander in san diego airspace, even if clear of class B airspace. I know the FAA would see this as my fault, but can procedures be standardized?

Related reports:

• Low time CFI goes IMC in VFR flight and experiences an unaut...
• A B737-300 flight crew experiences an unauthorized penetrati...
• Pilot of AS55 experiences near midair collision near bvi, af...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: AN AC14 PLT EXPERIENCES AN UNAUTH PENETRATION OF AIRSPACE, THE CLASS D OF MYF AFTER A NO HDOF FROM SAN APCH.

Narrative: VFR FLT TO MYF VIA V23. FLT FOLLOWING PROVIDED BY SOCAL APCH. MY PLAN WAS TO PROCEED TO MISSION BAY VOR AT 2500 FT THEN DIRECT TO MYF. CTLR REQUESTED THAT I TURN DIRECT TO MYF ABOUT 2 MI PRIOR TO VOR. I COMPLIED. FLT FOLLOWING WAS CANCELED AND I WAS TOLD TO CONTACT MYF TWR. BY THE TIME I CONTACTED MYF TWR, I WAS IN THEIR CLASS D AIRSPACE. TWR CTLR TOLD ME TO NOT ENTER CLASS D WITHOUT THEIR APPROVAL (WHICH IS CORRECT). FACTORS: 1) SOCAL CTLR WAS VERY BUSY SEPARATING HIGH SPD MIL TFC AND OTHER ACFT, VFR AND IFR. 2) AIRSPACE WAS VERY CONGESTED WITH IFR/VFR ACFT. 3) MYF WAS RPTING 2500 FT SCATTERED, 3000 FT BROKEN. 4) IT WAS DIFFICULT TO RAISE MYF DUE TO FREQ CONGESTION. 5) I HAD NO IDEA THAT HDOFS WERE NOT MADE BTWN APCH AND TWR AS AT SOME OTHER FACILITIES FOR VFR ACFT (OAKLAND, MONTEREY, RENO, PALM SPRINGS). 5) IT IS EXTREMELY DANGEROUS TO JUST WANDER IN SAN DIEGO AIRSPACE, EVEN IF CLR OF CLASS B AIRSPACE. I KNOW THE FAA WOULD SEE THIS AS MY FAULT, BUT CAN PROCS BE STANDARDIZED?

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.