Jump to content
View in the app

A better way to browse. Learn more.

Baseops Forums

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.

Featured Replies

You're right, it doesn't, I just used it to make the calculation without having any other known variables (i.e. FAF alt) assuming a 850 FPM VVI (rounded to 900).

ETA: I'm too dumb to do trig without a calculator if that's what you are implying. Using speed to figure nm/min to find time on final to use with FPM is much easier.

Holy shit Kenny, you're making this too difficult.

Edited by Danny Noonin

  • Replies 160
  • Views 64.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • 1. An aircraft with limited visual signature moving at 400kts is a (not 'the') hazard, just as every other thing in the sky is a hazard. That's a general comment made with absolutely no reference to

  • This. Not too long ago, several bros and I were sitting on the back porch with some drinks, talking about how some dude had recently porked something away to the point of *almost* killing himself an

  • Holy Monday morning f'ing quarterback. 1.). If you are a USAF pilot and haven't flown an F prefix, read your post, and think carefully if it applies. 2.). If you are in pilot training, just punch

Posted Images

Whatever dude, it's not difficult. Just used some numbers from everyday flying to give a realistic number.

Correct it is not difficult, but you make it so with your ineptitude. You are wrong and need to stop giving any input on this topic. Sit back and let the grown ups talk.

post-8431-0-54971700-1437018341_thumb.jp

That escalated quickly; do you guys know each other?

Not to beat a dead horse but piling on to my previous thread - how many GA/CFI types have logged 1/1000 the time most of us have flying formation? How many ranging exercises have they flown? How much are they used to looking out the window and seeing another aircraft near them?

Yeah, that's why some idiot private pilot will nonchalantly say that "fighter jocks" fly over their 2K' strip at 300 feet or claim a viper got within 50 feet of them in a MOA. Such an opinion is worth nothing.

That escalated quickly; do you guys know each other?

Not to beat a dead horse but piling on to my previous thread - how many GA/CFI types have logged 1/1000 the time most of us have flying formation? How many ranging exercises have they flown? How much are they used to looking out the window and seeing another aircraft near them?

Yeah, that's why some idiot private pilot will nonchalantly say that "fighter jocks" fly over their 2K' strip at 300 feet or claim a viper got within 50 feet of them in a MOA. Such an opinion is worth nothing.

But how does that effect a 3 deg wire from FAF to EOR...I think we're all missing the point here

Deleted my post to clean up thread, should be something learned here, not this bullshit. The content is in the quoted posts.

ing ridiculous.

Edited by Kenny Powers

Herc math here: ground speed/half. 120 ground speed = ~600 VVI. Done. You're welcome.

So Whitman and Kenny have both proven that they need to be put in time out...

Charleston is actually -600' MSL, so his math checks.

Your weak attempt at sarcasm is noted. Field Elev is -46 MSL at CHS. 10 miles x 3 = 3000 AGL. Easy. Done. No LGPOS math required.

Edited by Whitman

It's important for aviators to know their environment. The C-27 vs Herk out near Pope is another example of crews oblivious to each other.

Keep scanning you all, it may be the only thing that saves you one day.

Out

Lots of dumb shizz going on here.

As I previously mentioned, F-16 was at MVA (1,600 MSL). Field elevation accounting for normal day at CHS is approx 90 feet on the standby altimeter.

Lots of dumb shizz going on here.

As I previously mentioned, F-16 was at MVA (1,600 MSL). Field elevation accounting for normal day at CHS is approx 90 feet on the standby altimeter.

I'm sorry but ATC better have a damn good reason for having him this low at 20NM out, especially given that MSA is 3100ft. 1600 MSL is glideslope intercept altitude for R-15. That happens at 5.8 DME. Anyway, enough said. It will all come out in a few months. Just sucks 2 lives were lost and one ruined.

I'm sorry but ATC better have a damn good reason for having him this low at 20NM out, especially given that MSA is 3100ft. 1600 MSL is glideslope intercept altitude for R-15. That happens at 5.8 DME. Anyway, enough said. It will all come out in a few months. Just sucks 2 lives were lost and one ruined.

oh for fucks sake.

What does MSA have to do with vectoring altitude? Do you know what MSA means?

Edited by Danny Noonin

I'm sorry but ATC better have a damn good reason for having him this low at 20NM out, especially given that MSA is 3100ft. 1600 MSL is glideslope intercept altitude for R-15. That happens at 5.8 DME. Anyway, enough said. It will all come out in a few months. Just sucks 2 lives were lost and one ruined.

Have you tried looking at the instrument approach procedures into CHS before coming up with this stuff?

https://skyvector.com/files/tpp/1507/pdf/00076IL15.PDF

Edited by icohftb

I'm sorry but ATC better have a damn good reason for having him this low at 20NM out, especially given that MSA is 3100ft. 1600 MSL is glideslope intercept altitude for R-15. That happens at 5.8 DME. Anyway, enough said. It will all come out in a few months. Just sucks 2 lives were lost and one ruined.

Have you ever flown vectors to final?

Is this BODN or the comments section on a CNN plane crash article?

Why insult CNN?

"sorry that article is no longer available"

ETA: is the the article you were trying to link? https://www.live5news.com/story/29578829/ntsb-releases-preliminary-report-on-collision-of-cessna-and-f-16

ETA 2: well, that article is certainly an interesting read, to say the least. The ATC transcript especially.

Edited by stract

I'm glad we live in an age where we can be informed of these incidents almost immediately online. Looks like another example of a lot of things going wrong at the same time, although it's still to early to be sure about anything. No flight following of even a flight plan for the Cessna, and what appears to be a delayed compliance with ATC for the military pilot, combined with a 100 foot error in radar altitude. It will be interesting to see what the final report says. Just another example of the seriousness of the business and how small the sky really is.

I don't know if <30 seconds counts as delayed compliance. Especially if he didn't hear/register the 2 miles part. Especially while heads down in a single seat fighter. You don't usually get point outs as late as 2 miles for co-altitude, opposite direction traffic.

True man that's why I said "what appears to be" (or I guess I could have said "what would seem to me to be"). I mean for all we know he was diagnosing an issue with a system on the jet. I personally don't have any experience flying around in anything going faster than about 160 knots as of yet, I guess I'll be able to relate when I get to T-38s.

Edited by xcraftllc

I'm glad we live in an age where we can be informed of these incidents almost immediately online. Looks like another example of a lot of things going wrong at the same time, although it's still to early to be sure about anything. No flight following of even a flight plan for the Cessna, and what appears to be a delayed compliance with ATC for the military pilot, combined with a 100 foot error in radar altitude. It will be interesting to see what the final report says. Just another example of the seriousness of the business and how small the sky really is.

How is flying VFR part of "things gone wrong?"

Create an account or sign in to comment

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.