Mike, you frequently mention the simulator data base. I use X-Plane 11 , and even that data base I did not renew my database subscription and its out of date with numerous charts in a year or so. I had to pay a monthly subscription of 15 Euros to get it back up to date for practicing with current charts. For your videos, I simply place X-Plane 11 at you departure and duplicate your entries into the Garmin 530. I use a Stand Alone Garmin 530 so I twist knobs and press buttons exactly as its done in a real cockpit. Those twists and presses are essential to get your brain into gear thru time and repetition.
Very nice videos, thank you! Reference the TERPS climb requirements, basic (200'/NM) or specific in the ODP; most general aviation aircraft climb performance charts are expressed in feet per minute vs. feet per nautical mile. The formula for converting FPM to F/NM is ROC/(SPDK/60). The rate Of Climb is from the AFM, the climb speed will also be in the AFM performance or limitations. If expressed in MPH, it must be converted to Knots per Hour.
Yep, that's true. I also demonstrate the Rate of Climb/Descent gradient table that's on the last page of the Digital Terminal Procedures Supplemental document (available for free online and in ForeFlight. And probably available in other documents as well). In that chart, you can look at the climb gradient expressed in ft/NM and determine the minimum climb rate required to make that gradient, depending on your ground speed. I suggest going to the next greater gradient and/or speed rather than trying to interpolate. I also teach that chart in relation to the required descent rate to stay on a glide slope or glide path.
Great video as always Mike. I've run into some issues down at KSEE with the Mission Bay 2 Departure using my GNS430. In actual conditions, I prefer to turn the autopilot on before I start my turn (in a 310Q). It seems like a simple thing but switching from HDG to NAV just before the intercept on PGY has worked like a charm. Keeps me and the SCT boys in sync. Thanks!
Thanks, Steve! That's an interesting departure that I hadn't looked at before, thanks for the point-out. I'm guessing a bit, and it may depend on what autopilot you have, but if you press NAV too soon, your autopilot will probably take up a heading of around 210º for the intercept, while the procedure seems to want more like a 90º intercept angle. I'll have to experiment a bit... I sure like the 310s, though; I've started flying a P-model recently and forgot how much I like how they fly. Nice plane!
Joining DINGO5 to RNAV3 at KTUS. For the trip to KTUS and STAR enter the KFUL KTUS first then enter the DINGO5, then enter the approach for RNAV 3, you find a MAVVA transition. That fixes that RV dashed line between MAVVA and ALMON. Hope that helps. Generally there is a transition that align.
Yep, that's a good solution! I just happened to grab a VFR flight plan that I had saved in ForeFlight, and add the STAR to that. Often, but certainly not always, there is a STAR that ends at an IAF for at least one approach. If you start with the SID and STAR you want to use, then it's a simple matter to find a routing that connects the two, and run with that.
The Olympia arrival to BFI gives a heading from FOURT “for vectors to final.” If then flying an RNAV GPS approach, would this be a rare case where you would activate vectors to final for the approach? Or would you still leave the routing and fly headings and activate legs?
I would still be inclined to load the full approach from an IAF. If you load VTF, you'll still end up with only the FAF and the MAP in the flight plan, and if you got a vector to some fix outside the FAF (i.e., JUGOK on the RNAV (GPS) 14R), you'd be scrambling to load it at that point. If you got vectored inside of JUGOK, it's so easy to activate that leg when you get that clearance. I prefer to leave the fixes in there as I get the vectors, as it helps me to stay oriented within the procedure.
Never loaded a SID to my 530W although I used them. Now I am ready. Thank you Mike.
Awesome! Go get 'em!
Mike, you frequently mention the simulator data base. I use X-Plane 11 , and even that data base I did not renew my database subscription and its out of date with numerous charts in a year or so. I had to pay a monthly subscription of 15 Euros to get it back up to date for practicing with current charts.
For your videos, I simply place X-Plane 11 at you departure and duplicate your entries into the Garmin 530.
I use a Stand Alone Garmin 530 so I twist knobs and press buttons exactly as its done in a real cockpit.
Those twists and presses are essential to get your brain into gear thru time and repetition.
hello cpt Mike, I just got hired to fly C402 in Cape Cod and your videos are helping me a lot. Thanks a lot for your videos
Congratulations on getting a flying job! And I’m very glad you’re finding our programs helpful. Best of luck!
I used to fly 310s & 402s to ACK & MVY. Enjoy the ride and remember "fog happens".
Very nice videos, thank you! Reference the TERPS climb requirements, basic (200'/NM) or specific in the ODP; most general aviation aircraft climb performance charts are expressed in feet per minute vs. feet per nautical mile. The formula for converting FPM to F/NM is ROC/(SPDK/60). The rate Of Climb is from the AFM, the climb speed will also be in the AFM performance or limitations. If expressed in MPH, it must be converted to Knots per Hour.
Yep, that's true. I also demonstrate the Rate of Climb/Descent gradient table that's on the last page of the Digital Terminal Procedures Supplemental document (available for free online and in ForeFlight. And probably available in other documents as well). In that chart, you can look at the climb gradient expressed in ft/NM and determine the minimum climb rate required to make that gradient, depending on your ground speed. I suggest going to the next greater gradient and/or speed rather than trying to interpolate. I also teach that chart in relation to the required descent rate to stay on a glide slope or glide path.
Another great training video!!!!, as always I learned a lot. Thanks
Great video as always Mike. I've run into some issues down at KSEE with the Mission Bay 2 Departure using my GNS430. In actual conditions, I prefer to turn the autopilot on before I start my turn (in a 310Q). It seems like a simple thing but switching from HDG to NAV just before the intercept on PGY has worked like a charm. Keeps me and the SCT boys in sync. Thanks!
Thanks, Steve! That's an interesting departure that I hadn't looked at before, thanks for the point-out. I'm guessing a bit, and it may depend on what autopilot you have, but if you press NAV too soon, your autopilot will probably take up a heading of around 210º for the intercept, while the procedure seems to want more like a 90º intercept angle. I'll have to experiment a bit... I sure like the 310s, though; I've started flying a P-model recently and forgot how much I like how they fly. Nice plane!
Great new info and review mike.
Joining DINGO5 to RNAV3 at KTUS.
For the trip to KTUS and STAR enter the KFUL KTUS first then enter the DINGO5, then enter the approach for RNAV 3, you find a MAVVA transition. That fixes that RV dashed line between MAVVA and ALMON. Hope that helps. Generally there is a transition that align.
Yep, that's a good solution! I just happened to grab a VFR flight plan that I had saved in ForeFlight, and add the STAR to that. Often, but certainly not always, there is a STAR that ends at an IAF for at least one approach. If you start with the SID and STAR you want to use, then it's a simple matter to find a routing that connects the two, and run with that.
Thank you
The Olympia arrival to BFI gives a heading from FOURT “for vectors to final.” If then flying an RNAV GPS approach, would this be a rare case where you would activate vectors to final for the approach? Or would you still leave the routing and fly headings and activate legs?
I would still be inclined to load the full approach from an IAF. If you load VTF, you'll still end up with only the FAF and the MAP in the flight plan, and if you got a vector to some fix outside the FAF (i.e., JUGOK on the RNAV (GPS) 14R), you'd be scrambling to load it at that point. If you got vectored inside of JUGOK, it's so easy to activate that leg when you get that clearance. I prefer to leave the fixes in there as I get the vectors, as it helps me to stay oriented within the procedure.