View Single Post
  #10  
Old May 3rd 07, 11:51 AM posted to rec.aviation.piloting
Steven P. McNicoll
external usenet poster
 
Posts: 1,477
Default Flight Following and OOPS


"Mike 'Flyin'8'" wrote in message
...

I am not sure what I should do with this, so I am fishing for
opinions, thoughts etc.

I took off from an airport and immediatly requested and received VFR
flight following through some Class C which lies between my current
position and my destination. I climbed to 5500 +/- 100ft and was
vectored through the Class C. When I was near the edge of the Class C
( I estimate I was 2-3 miles from the edge of exiting the Class C) I
was asked if I can resume own navigation, and report destination
airport in sight, I reported airport in sight and the controller told
me "resume own navigation, squak VFR, Radar services terminated"

I flew along for a short time and noted I was below the 5500 ft
ceiling of the class C (by around 100ft) and immediatly climed to
5600ft for the remaining couple miles.

So... Obviously I was in the Class C, and though I was still on
approach frequency, I do not think that I was still in radio contact,
right?

Is a NASA ARS form appropriate? Was I wrong and did I bust the C?


You weren't wrong, you didn't bust Class C airspace, you didn't need to
climb back up, and you have no need of a NASA form. Controllers are
supposed to terminate Class C service to aircraft landing at satellite
airports within Class C airspace or the associated outer area at a
sufficient distance from the airport to allow the pilot to change to the
appropriate frequency for traffic and airport information. FAR 91.130
requires radio communications while within Class C airspace, but like most
FARs dealing with ATC it begins with the phrase "unless otherwise authorized
by ATC."


http://www.faa.gov/airports_airtraff...708.html#7-8-8


§ 91.130 Operations in Class C airspace.

(a) General. Unless otherwise authorized by ATC, each aircraft operation in
Class C airspace must be conducted in compliance with this section and
§91.129. For the purpose of this section, the primary airport is the airport
for which the Class C airspace area is designated. A satellite airport is
any other airport within the Class C airspace area.

(b) Traffic patterns. No person may take off or land an aircraft at a
satellite airport within a Class C airspace area except in compliance with
FAA arrival and departure traffic patterns.

(c) Communications. Each person operating an aircraft in Class C airspace
must meet the following two-way radio communications requirements:

(1) Arrival or through flight. Each person must establish two-way radio
communications with the ATC facility (including foreign ATC in the case of
foreign airspace designated in the United States) providing air traffic
services prior to entering that airspace and thereafter maintain those
communications while within that airspace.

(2) Departing flight. Each person-

(i) From the primary airport or satellite airport with an operating control
tower must establish and maintain two-way radio communications with the
control tower, and thereafter as instructed by ATC while operating in the
Class C airspace area; or

(ii) From a satellite airport without an operating control tower, must
establish and maintain two-way radio communications with the ATC facility
having jurisdiction over the Class C airspace area as soon as practicable
after departing.

(d) Equipment requirements. Unless otherwise authorized by the ATC having
jurisdiction over the Class C airspace area, no person may operate an
aircraft within a Class C airspace area designated for an airport unless
that aircraft is equipped with the applicable equipment specified in
§91.215.

(e) Deviations. An operator may deviate from any provision of this section
under the provisions of an ATC authorization issued by the ATC facility
having jurisdiction over the airspace concerned. ATC may authorize a
deviation on a continuing basis or for an individual flight, as appropriate.

[Doc. No. 24458, 56 FR 65659, Dec. 17, 1991, as amended by Amdt. 91-232, 58
FR 40736, July 30, 1993; Amdt. 91-239, 59 FR 11693, Mar. 11, 1994]