Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
SID and ODP climb gradients are based on all engines operating, and extrapolating second-segment climb data to the top of the SID doesn't really work...despite what so many schoolhouse instructors teach.
http://www.nbaa.org/ops/safety/climb-performance/
If you can meet the climb gradient of the ODP all engines operating, you'd be legal...but if you bag one then you need to have an suitable out to ensure you don't end up in cumulogranite (and to avoid that whole 91.13 thing previously mentioned). If you can see the tops of the terrain you can maintain separation visually, but if IMC the APG departure procedure is a legal means by which one can maintain obstacle clearance in a OEI situation.
True but what good does this fact do for you when you lose an engine at V1? Conservative is good, no old bold pilots.
Also true but technically you can do almost anything you want when operating Part 91 so long as nothing goes wrong. That's when the ol' 91.13 comes into play. That's where the "Other" category comes into play. The published takeoff mins for folks that can't make the climb gradient are to ensure a visual return to the field.
ASPEN, CO KASE *
* ASPEN-PITKIN CO/SARDY 17 Sep 09 *
* *
* *
* Rwy TAKEOFF WEIGHTS FOR RWY 33DP REQUIRE USE OF *
* 33DP THIS TAILORED DEPARTURE PROCEDURE: *
* *
* TAKEOFF WEIGHTS FOR RWY 33DP REQUIRE *
* USE OF MODIFIED PUBLISHED -LINDZ- AND *
* -SARDD- DEPARTURE PROCEDURES. *
* *
* MAKE AN IMMEDIATE 15 DEGREE BANKED CLIMBING *
* -RIGHT- TURN TO A HEADING OF 340 DEGREES. *
* *
* *
* AT 10.3 DME SOUTH OF DBL VOR TURN -LEFT- *
* TO A HEADING OF 270 DEGREES. *
* *
* INTERCEPT THE IPKN LDA NORTHWEST COURSE *
* (OUTBOUND ON BACKCOURSE) DIRECT LINDZ *
* INTXN (DBL VOR 244/13.0). *
* *
* CLIMB IN HOLDING PATTERN AT LINDZ INTXN. *
* (WEST, LEFT TURNS, 064 INBOUND). *
* *
* *
**************************************************************************
**************************************************************************
* These procedures describe the non-standard, one engine *
* inoperative, departure flight path. The maximum allow- *
* able takeoff weights, presented in the attached analysis, *
* are based upon the procedure(s) outlined above.
-We NEVER circle to land on Runway 33, but I know some people do in turboprops.
-We NEVER operate in or out at night.-I've never been able to make the climb gradient coming out of KASE so we use the "OTHER" category takeoff mins as our required weather for departure.
-We ALWAYS depart 33, if tailwind is too much we park.
-We ALWAYS include escape plan in TO brief for engine failure. Basic plan is fly up the right (east) side of the valley and turn left (west) at the valley exit and fly I-70 to KRIL.
Check your PM for specifics on approach that I don't want to cut and paste from SOP over open forum.
You fly the APG departure procedure when OEI, you will remain clear of terrain provided you were at or under the max weight shown in the analysis for the conditions & the Runway DP.
APG data gives you a safe and legal "out" in the instance something *does* go wrong...and having a runway analysis which supports your actions kinda takes away the FAA's argument about careless-and-reckless operation.
Here's the quote directly from APG:
[/COLOR]
Both of my comments about your posts were referencing NOT using an APG.
I can't advise making your first couple trips to/from ASE in IFR which would negate the need for an APG.
JS,
I also slow down and configure early on the approach. There is nothing worse than being high and fast and behind the 8-ball going into ASE. So, we are slowed and in landing config at Red Table.