Narrative:

Departing myf; requested and received from myf ground control a miramar (nkx) transition northbound for class B. We acknowledged and were told nkx tower was closed and 'when able' to contact socal on 125.3 for flight following. We informed the myf tower we would stay at 2;900ft MSL to avoid the overlying class B at nkx. When established northbound over nkx we attempted to contact socal on 125.3. I was pilot flying from the right seat and was concentrating on traffic; course and altitude. The controller (125.3) did not respond to our initial call as he was communicating with multiple aircraft. The clearance from myf tower implied that contact with socal was optional as nkx tower airspace was closed. Thinking we were under the overlying class B at 2;900ft MSL we continued to monitor 125.3 when socal made a blind call to an 'aircraft northbound over nkx to squawk ident'. That being our relative position we acknowledged the call. The controller informed us that we had in fact not received a class B clearance and to make a turn back toward myf. We complied immediately and turned southbound at 2;900ft. MSL. The socal controller informed us that there was no conflict and the miscue was not a problem. He explained to us that when nkx tower was closed that socal (125.3) becomes responsible for controlling the nkx underlying airspace. The controller reiterated to us that it was no problem and to consider it a learning experience. He then asked us to contact myf tower. We called myf to request overflight of their class D at 2;900ft MSL which they approved and we gave us clearance to proceed to the shoreline. I feel that do to the nonstandard departure procedure do to the closure of the nkx tower that myf tower could have been more precise in the fact that socal was now 'controlling' the airspace normally controlled by nkx. Kudos to socal for the explanation and treating this as a learning event. I immediately shared this event with other pilots at my company to prevent this in the future. It has been brought to my attention by a controller from another san diego ATC facility who has experience in this 125.3 socal sector that this is not an uncommon event and not surprised of the miscue and confusion.

Google
 

Original NASA ASRS Text

Title: Pilot reports of violating airspace. Controller told pilot to contact approach control and that a tower was closed. Pilot thought it was optional to contact Approach. Approach called out in the blind for pilot to ident. Pilot was told by approach that he should have called and the they should have asked for a Class Bravo clearance. ATC explained issue to pilot and a learning experience and did not violate the pilot.

Narrative: Departing MYF; requested and received from MYF ground control a Miramar (NKX) transition northbound for Class B. We acknowledged and were told NKX Tower was closed and 'when able' to contact SOCAL on 125.3 for flight following. We informed the MYF Tower we would stay at 2;900ft MSL to avoid the overlying Class B at NKX. When established Northbound over NKX we attempted to contact SOCAL on 125.3. I was pilot flying from the right seat and was concentrating on traffic; course and altitude. The controller (125.3) did not respond to our initial call as he was communicating with multiple aircraft. The clearance from MYF Tower implied that contact with SOCAL was optional as NKX Tower airspace was closed. Thinking we were under the overlying Class B at 2;900ft MSL we continued to monitor 125.3 when SOCAL made a blind call to an 'aircraft northbound over NKX to squawk ident'. That being our relative position we acknowledged the call. The controller informed us that we had in fact not received a Class B clearance and to make a turn back toward MYF. We complied immediately and turned southbound at 2;900ft. MSL. The SOCAL controller informed us that there was no conflict and the miscue was not a problem. He explained to us that when NKX Tower was closed that SOCAL (125.3) becomes responsible for controlling the NKX underlying airspace. The controller reiterated to us that it was no problem and to consider it a learning experience. He then asked us to contact MYF Tower. We called MYF to request overflight of their Class D at 2;900ft MSL which they approved and we gave us clearance to proceed to the shoreline. I feel that do to the nonstandard departure procedure do to the closure of the NKX tower that MYF Tower could have been more precise in the fact that SOCAL was now 'controlling' the airspace normally controlled by NKX. KUDOs to SOCAL for the explanation and treating this as a learning event. I immediately shared this event with other pilots at my company to prevent this in the future. It has been brought to my attention by a controller from another San Diego ATC facility who has experience in this 125.3 SOCAL sector that this is not an uncommon event and not surprised of the miscue and confusion.

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.