Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RedSpinnaker

Members
  • Joined

  • Last visited

Everything posted by RedSpinnaker

  1. You're right...Damn attention to detail after a bottle of wine...
  2. Stepping out of CONUS...and a non-circling... I see your 6.8 degrees, and raise you 9.3 degrees: VNKT VOR DME RWY 02 BTW: Thanks for the ARINC clue... Didn't think about encoding fixes in the database...
  3. The VOR/DME or TACAN Z RWY 15 into MTN is not a military only procedure. I don't know why it's not in the raw database, but that doesn't preclude it being available for civilian use. Without doing more digging, the only thing that immediately comes to mind is AC 90-108 - Use of Suitable Area Navigation (RNAV) Systems on Conventional Routes and Procedures which is what allows using RNAV (GPS) in lieu of DME. The language has made it into the AIM, specifically 1-2-3-c (Note: 4): MTN is a rare approach (with an arc as the final approach segment). Here's my blind leap (which may be incorrect)...Since RNAV/GPS is being used in lieu of DME, and DME is what is providing lateral guidance on the final approach segment, it's not authorized. This still doesn't necessarily explain why it's left out of the raw database. It's been awhile (years) since I've dug into RTCA specs & requirements. I'm not sure if there is a database flag that prevents an approach from being flown until certain sensors are present (i.e. what if I'm in a a/c WITH a separate DME, and want to display an approach overlay for SA?). Perhaps they don't include it in the database to prevent someone using the approach in GPS mode when it's obviously not authorized due to the final segment? Don't know.. spitballing here. Would need more time to dig deeper.
  4. Yeah, 11.. sorry... typo... was still on my first cup of coffee.
  5. 1200 ft has nothing to do with it. You can abandon an instrument approach and proceed visually at any point (assuming certain criteria are met). However, yes, on this approach, if I saw the airport and could proceed visually to land. I wouldn't forget about the arc, rather I'd probably be thinking about the 10 DME arc in the back of my mind. Though outside of training, I'd shoot one of the other approaches (LOC/LDA/RNAV) as they all have lower mins.
  6. You'd continue flying the 14.7 DME arc and descending to 900'. Upon crossing the BAL 060 radial at or above 900', then you'd execute the missed. The MAP is ~3.3 miles from the 047 radial (ZOVAP), and with the lowest mins requiring 1 mile, still need guidance to get closer. Remember flying this years ago during my multi- training. Losing (simulated) an engine inside the FAF, and then shooting the missed onto another arc and the hold was sporty...
  7. Oh, please don't take what I was saying as a complaint. I have the V2 Legacy and love it. I was just commenting in reference to the turbocharged variant. Experimental + Fast = Someone will always find a way to make it go faster.
  8. I don't want the turbocharged Legacy... I want the turboprop Legacy... http://generalaviationnews.com/2015/08/06/around-the-field-at-airventure-oshkosh/
  9. Bryan, My fault, sorry about that. Although the Approach Brief did have ASDEX selected, the TARA ASDEX option was turned off. Must have missed it when clicking through all the individual options.
  10. Bryan, Could this bug also contribute to not leaving the transponder ON after landing, despite briefing that the airport does have ASDE?
  11. Obviously you're not a lawyer, or have had experience with them post incident.
  12. http://www.avsim.com/topic/481134-virtual-avionics/
  13. I REALLY miss FSRecorder's rendering mode in the alpha version for FSX...Too bad development didn't continue through P3D That was truly a have your cake and eat it too tool...
  14. Gotcha... That's what I thought you were saying.. Thanks!
  15. I've decided to go the second 980Ti route and run in SLI (along with the costs of a new mobo and case) as it'll allow for more flexibility long term. You mention FSX.. however earlier you mentioned the second 980Ti resolved your microstuttering in heavy wx with your 4K display. Was that P3D? Thanks!
  16. Recently moved to a 50" 4K display (don't think I'll ever go back). Started experiencing some microstuttering (running single 6GB 980Ti). Do you think going with a single TITAN Z would result in similar performance as twin 980Ti's (SLI)? The reason for the question is my current rig is an mITX build. So, if I have to go the SLI route, it's a whole new build (and I'll likely jump down the dual loop liquid cooling rabbit hole again). So, spending $$ either way. Just curious if the TITAN Z would be worth it, or I should just pull the trigger for a new build.
  17. Definitely have to agree. I just made the jump to 4k yesterday, and am impressed. Still sorting some of the graphics settings, but overall it was a good move. Having done the single screen (1080) -> triple screen -> single screen (1440) -> 4k, I'm glad I did. Went with a Samsung UN50JU6500 and still working through the TV settings.. Anyway, other than running a 210 degree wraparound display w/ 3-4 projectors, this is the next best thing Well, until Oculus in a couple months I think...
  18. Not 7", but I use this and love it... http://www.amazon.com/gp/product/B00PYWSYDE
  19. Very Nice! I've always thought being in the air for a sunrise was more enjoyable than a sunset.
  20. Does what, external camera mounts?
  21. Video of a flight I did up the East Coast last summer.
  22. Seems to be working here... Thank you for the quick fix!
  23. Jim, Thanks! Appreciate the quick reply. Have a good day.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.