UltraNav works well for WT&Bal computations and for determining what your 2nd segment OEI climb capabilities are (theoretically). It also can be used in the cockpit and can be used for landing data.
What APG offers is a OEI climb capability for a specific procedure that allows you to clear terrain IAW TERPS terrain seperation criteria vs FAA terrain seperation criteria.
No it doesn't. APG is giving you Part 25, single engine, obstacle clearance data. It will offer an alternate procedure, if it will allow for an increase in takeoff weight. It's not IAW TERPS. APG also shows you different scenarios like what an increase or decrease in temperature will allow you to do. Takeoff weight is adjusted for various factors, including runway contamination, pressure changes, winds, temperature, flap selected and bleeds. Also corrections are factored for inoperative equipment, like anti-skid and ground spoilers inop. I like the fact that APG determines what climb gradient is required and tells me what weight I need to be at given the current range of temps to make that gradient.
Yeah, it's giving you obstacle clearance for current conditions!
(Obama Voice ON) Let me be perfectly clear! (Obama Voice OFF):nuts: The terrain seperation figures that APG gives you are NOT safer than waiting for the weather to get up to takeoff mins (for us 91 guys). You must fly the procedure. That means that when the procedure differs from the SID, you should file NO SIDS
WTF you taking about? You file as normal, lose an engine, declare an emergency, and deviate as planned. You do not fly the emergency departure procedure, all engines running! in remarks, and file to the last waypoint along the departure path that APG has calculated for you. Most times the APG procedure follows the SID
maybe alternate procedure, standard is straight out, to 30 miles, so this is not an issue. But many people had the thought in their head that they would fly the SID and if they lost an engine they would declare an emergency and fly the APG procedure. That ain't how it works
Yes it is!. Take KEGE for instance. The APG procedure used to be the "Cottonwood Departure" If you took off on the Gypsum Departure and lost an engine after making the turn to 215 degrees, you were in no man's land trying to manuever over to the Cottonwood departure's path (there is a huge mountain in between for those not familiar). I think that APG has since made their departure overlay the Gypsum.
Little more than that. Besides holding at VAILE, and climbing, it also requires a non-standard (for single-engine) bank angle, and airspeed restrictions.
On rare occasion, the APG departure will actually bring to your attention a situation that is restrictive, that may have escaped your attention before. KAPF is a good example of this. On the chart, Rwy 5 length is 5290ft long, but the the TORA is only 5000ft. Rwy 14 is 5000ft long, but the TORA is only 4550
You may want to re-read the TORA/TODA? because of this:
Naples Muni
RUNWAY DECLARED DISTANCE INFORMATION
RWY 05:
TORA–5000 TODA–5290 ASDA–5000 LDA–5000
RWY 14:
TORA–5000 TODA–5000 ASDA–4550 LDA–4420
RWY 23:
TORA–5000 TODA–5000 ASDA–5000 LDA–5000
RWY 32: TORA–5000 TODA–5000 ASDA–4870 LDA–4420
In this case APG would bring to your attention that there are obstacles that limit your RUNWAY LENGTH AVAILABLE for takeoff (ie TORA). This has nothing to do with climb gradient (actually it does - just not in the way we normally think). Jeppesen is starting to list the TORA, TODA, and ASDA on more and more charts, otherwise the only place that I know of to find it is in the AFD
Read the notes on the bottom of Jepps 10-9: Runways 23,14 and 32 state that the last 290', 450' and 130' respectively, is unusable for landing compulation (nor as a stopway). Can you figure out why the Runway 05, has a TORA of 5000' and TODA of 5290'?
If you could not tell by now, I highly recommend APG. And no, I do not work for them. boy, I'm glad!