GLOBAL HAWK BLOCK 30 REPRIEVE?

I know that a lot of lawmakers are pissed at the USAF for buying aircraft and subsequently storing them due to budgetary realignment and less than satisfactory operational performance, which is more or less an omission of a total waste of funds. Although the House Armed Services Committee seems to be drawing the line on this practice at the Block 30 Global Hawk, as they are electing to fund it’s operation going forward. I know the USAF says the U-2 does the Block 30 Global Hawk’s job better and more efficiently, but seeing that there is pretty much a consensus for needing more strategic ISR platforms, utilizing the abandoned Block 30 Global Hawks could not hurt.

If the complexity of the Block 30′s assigned missions are too much for the system to handle efficiently, than just stick a Battlefield Airborne Communications Node (BACN) on-board and other beyond line of sight communications systems and let them act as an airborne data-fusion platform and communications relay alone. Having an active net over a battle space that can translate the various languages coming from the variety of data-link modems and terminals the DoD has fielded is a very important job, and a high-altitude player like the RQ-4 is a perfect system to employ such a capability. Northrop Grumman engineers already know this and have tested the Block 30 RQ-4/BACN combo in the EQ-4B configuration. Even the Navy’s Global Hawk Block 40 “Broad-Area Maritime Surveillance” aircraft, otherwise known as BAMS, will have BACN built-in, along with pretty much everything and “the kitchen sink” of ISR capabilities. This is great, but a single BAMS aircraft can be in only one place at one time, why not put it’s little brother to work on less dynamic mission sets such as the humble yet vitally important BACN role alone? It just seems ridiculous to me that we purchase these assets and decide not to use them, even if we do so in a lesser role or at a lower frequency.

http://defense.aol.com/2012/04/25/hasc-orders-air-force-to-fly-its-block-30-global-hawks-260-mil/

All you need to know about the Global Hawk Block 40 BAMS:

This entry was posted in News, Opinon and tagged , , , , , , , , , , , , , , , , , , , , , , , , , , , , , . Bookmark the permalink.

5 Responses to GLOBAL HAWK BLOCK 30 REPRIEVE?

  1. FlightDreamz says:

    Interesting enough, now that the U-2 Dragon Lady’s are taking the more of the burden, decompression illness seems to becoming more of an issue see http://www.airspacemag.com/military-aviation/Killer-at-70000-Feet.html and
    http://www.ncbi.nlm.nih.gov/pubmed/8775396
    Apparently the increased workload in the cockpit is bring on decompression sickness more readily.

  2. aviationintel.com says:

    I am looking at this now, thanks so much Flight Dreamz!

    Ty

  3. FlightDreamz says:

    Interesting enough, now that the U-2 Dragon Lady’s are taking up more of the burden, decompression illness seems to becoming more of an issue see http://www.airspacemag.com/military-aviation/Killer-at-70000-Feet.html and
    http://www.ncbi.nlm.nih.gov/pubmed/8775396
    Apparently the increased workload in the cockpit is bring on decompression sickness more readily.

  4. FlightDreamz says:

    Ooops! Double post (sorry about that)!
    My understanding that since U-2′s are in such high demand right now (war on terror and all that) instead of flying to their designated area doing a recon run and returning to base. Pilots are now having to do more “on the fly” (if you’ll excuse the expression. Really enjoy reading the posts on your website, thanks for allowing me to throw my two cents into the conversation.

  5. aviationintel.com says:

    Thanks so much Dreamz, I have heard the same and the new avionics apparently really help with re-planning on the fly.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>