Thanks for elaborating. That was helpful and worth a good discussion. I can split the thread if needed.
Flying day VFR HAA in a twin engine IFR capable helo at 700/2 made no sense to me.
Understandable, but depending on the program, you're never going to be able to go IFR for all the places you need to get to. IFR can have it's value overall, but it seems to provide significantly more value in mountainous terrain versus flat terrain with good roads. That said, no matter where the program is, being able to get that freeway or random farmer's field will always have value and more times than not, won't be solved by a PINS approach.
I suppose the FAA could generate 100's of let-down points, but even then, with how big our country is, I'm not sure you'd still be able to get close enough and still meet the spirit of 135.613. Yes, the numbers could change, but not by a lot before you're already at .609 minimums (and still maintaining a safety level that's better than the industry historic numbers).
First - we need a low alt en-route structure with lower MEA's - kind of like RVSM for jets only in reverse and let ATC own separation services without having to fly at 5000'. ADS-B and WAAS makes it possible for finally a lower altitude enroute structure
Don't the GPS airways do this? Granted there could be more of them, but the GPS airways do have significantly lower MEAs. I'm not smart on what a "MVA" is for ADS-B. I'm sure it's lower than with an ASR, but there still has to be line-of-sight at some point, which is going to keep the overall MEA relatively high (greater than 1000' AGL).
Also, how do you get much lower and still maintain the safety margin of 1000'/2000' for terrain/obstacles? It seems the GPS airways try and makeup for this, but you can only get so low and still be a) effecient in routing and b) not hit a cliff. It seems like we're back to the same idea of needing more of them.
Second, more rapid development of COPTER PINS approaches to places like hospital helipads - something that doesnt take years to develop and are well coordinated. You've likely seen in your current job how slow it is to develop approaches and then get approved - same for ODP's from heliports.
I certainly don't have my finger on the pulse of my company's Ops, but from the emails I see (and when I've asked PINS-specific questions), it seems like the hold up has more to do with the FAA then with building the approaches. Obviously that's an issue for everything that has to get a stamp of approval in a bureaucracy. But that's a whole other rant that isn't specific to helos.
I think there's also the matter of copyright that slows things down. If a company has their approach built by someone who intends to keep the rights to the approach, that person can hold the approach ransom down the road, which increases cost (and/or time). That has certainly happened.
I know my company has moved away from copyright PINS approaches.
Third - WX reporting by geographical segment (think MEF figures in a sectional quadrangle only for weather reporting). AWOS/ASOS sucks and is complex to deploy. Something that doesn't revolve around a runway. Its doable - sensors, connectivity and non terrestrial solutions exist (modeling).
Additional METARs would certainly be helpful, but again, costs money. I know it's a complaint we have at our base. Your "weather quadrant" idea is a good one, but isn't that what the GFA tool is supposed to be doing now? I do wonder if we're just not quite there on the technology front to make the data more helpful. I'll occasionally play around with the GFA tool on nights when I'm expecting weather (but have no TAF at my base), but I find it to be hit and miss. I think part of why I don't trust it is because it will sometimes give me forecast data that's drastically different than the TAF that covers the exact same spot.