View Single Post
  #2  
Old March 29th 07, 05:05 PM posted to rec.aviation.piloting
[email protected]
external usenet poster
 
Posts: 2,892
Default A tower-induced go-round

Steven P. McNicoll wrote:

"Jose" wrote in message
t...

I haven't looked over the procedure in question, and the "problem I have"
isn't with the procedure, it's with the =idea= that a few locals can dummy
up a procedure that is in conflict with generally accepted flying
procedures (like the AIM) and with FAA mandated procedures (like an ODP if
it applies).


TAKE-OFF MINIMUMS AND (OBSTACLE) DEPARTURE PROCEDURES


SW-3
07074



UPLAND, CA
CABLE


TAKE-OFF MINIMUMS: Rwy 6, 300-1 or std. with a min. climb of 240' per NM to
1900.


DEPARTURE PROCEDU Rwy 6, climbing right turn. Rwy 24, climbing left turn.
All aircraft climb direct PDZ VORTAC. Aircraft departing PDZ R-091 CW R-140
and R-231 CW R-280 climb on course. All others continue climb in PDZ holding
pattern (E, right turns, 258? inbound) to cross PDZ VORTAC at or above:
R-281 CW R-090, 6700; R-141 CW R-230, 4000.


Yep, those are the IFR procedures.

Which part of the local procedures being for VFR are you having trouble
understanding?

The 24 IFR departure is identical to the 24 VFR departure to the South
except the IFR departure references a VORTAC while the VFR departure
references a VFR landmark. The path in the area of the airport is the
same in both cases.

The 6 IFR departure does not conflict with any VFR procedure.

The 6 IFR departure takes you immediately into class C airspace, while
the 6 VFR departure takes you away from it.

The 6 IFR departure would be illegal to do without a radio, and if
you did it with a radio, while legal, it would **** of the class C
tower which is expecting you to use the VFR procedure and call them
when you get close to midfield if you intend to cross their airspace.

The tower would direct you to follow a path that is roughly the same
as the VFR departure path though perhaps inside their airspace while
the VFR path keeps you out of it.

--
Jim Pennino

Remove .spam.sux to reply.