Jump to content

US Herk

Members
  • Posts

    391
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by US Herk

  1. I\'ve never had a major birdstrike myself - nothing with any significant damage. Have had several in the various units I\'ve been in like when I was in 52d, we had one through the center windscreen on a Red Route @ POB many years ago - SKE scope saved the FE on that one. I think one of only three documented center windscreen penetrations. P,CP,FE covered in blood & glass - think it was a turkey vulture too, so you know it stunk good!

    When I was at Hurbie, we had one go through the leading edge & into the spar in S. America - got one-time flight home & long repair.

    At Kirtland a few years back, we had a goose through the metal under the center windscreen - very messy as all the backs of the instruments got covered with that one.

    One at the 1st - 155K takeoff in the PI took well over 300 counted birdstrikes, lost #1 and #2 decayed to 70% and overtemped, but eventually recovered - needless to say, the crew didn\'t shut it down as they frantically dumped & came back around.

    I used to say there\'d never been a loss of a 130 due to birds, but I was recently informed of a Belgian 130 that crashed in the Netherlands. Had a flock of birds flush as they were coming in on approach, so they went around & lost power on three engines, rolled, & cartwheeled - almost all aboard died (Dutch band in the back!) - this was at Eindhoven in \'96...

  2. Something else to consider - the J was originally delivered w/o externals due to having the same, or increased range as a classic w/o them. This, however, was based on being able to climb to their optimum cruise altitude which is in the upper FL300s. ATC won\'t let them up there because they\'re too slow to mix it up with the airlines. Even the low FL300s are usually unobtainable due to short-range airline & mil-jet traffic.

    When kept below FL300, they end up burning more fuel & not realizing the speed increases they are capable of. The RAF\'s standard Lyneham-to-Akrotiri run is almost a wash J v K - the J does have the edge, but not by much...

  3. I believe the J has slightly re-designed CWB (I think some H3 have it too) using some of the upgrades of the SOF CWB. Don\'t know what the EBH limit is on the newer ones (SOF is 85K).

    Here at WR-ALC last week & this helping train them on T2 - saw 0011 in the jig getting ready to pull CWB with new one sitting next to it - apparently was delivered two weeks ago. Good to see first T2 getting a box (1212 doesn\'t count!)

    EDIT: \'92 & up do have strengthened CWB, but EBH limit is still the same. Current production J-models will be getting SOF-style CWB with increased EBH starting next year...

    ...this from the CWB bubbas here at WR-ALC today.

  4. Currently at Warner-Bubba helping 339th get MC-H through FCF & providing some MC-H specific training for them. Seen a few birds going through wombat conversion...

    Also saw 0011 sitting in the CWB jig (moved in yesterday) for first (new production) CWB for T2...

  5. Pre-66 the Tac-Trained Killers were probably flying fingertip vics in trail at 1000\' or so, right?

    I believe the Pope accident was one of the contributing factors to the move towards in-trail formation we do today. That and strat SAMs like SA2/SA3 with very large warheads, low-level tactics, etc. But the POB accident was the \"nail in the coffin\" that pushed the change if I have my history right...

  6. DC10FE wrote:

    Wow! Do they still preach that? I always thought that was a holdover from the recip days. I used to get jacked up all the time for that felony!!

    Don R.

    Yes - apparently the AFOSH isn\'t specific enough - there is a note for C-130 aircraft that w/o bleed air there is no danger. But people still teach it and put it in local sups \"just to be safe\" - like a Herk prop is just gonna start spinning...

    I understand habit patterns, but it\'s pretty obvious when the APU/GTC is running, or an M60 is hooked up & screaming or, better yet, an engine is running...most folks avoid all those things simply because of the noise alone!

  7. I don\'t, as a rule, randomly flip switches on the overhead panel. I think I probably do it about how Dan described. If the FE is in the back & an aux/ext tank went dry, I\'d have my co-pilot fix it under my supervision & inform the FE when he got back. If I\'m on a high-level cruise & want to teach something on the overhead panel to the CP, I make sure the FE is involved. I *might* tweak the temp (always check it\'s in auto first - old trick, Dan), but that\'s a rarity - and I would only do it if the FE is occupied (doing TOLD or out of his seat).

    SEFEGeorge wrote:

    After spending many years at the schoolhouse you are \"exposed\" to officers from many services and countries. Most of them had never flown a crew airplane and many had overblown egos. The tactful approach very seldom worked so the more \"aggressive\" approach got the best results. As an officer you\'ll probably contradict that.

    Nope, no contradiction there - plenty of big egos on the Officer side of the house & pilots tend to have it worse than others. That said, there\'s plenty of FEs who like to show how important they are in various ways. There\'s bad apples in every crew position, but to paint them all with the same brush is short-sighted.

    SEFEGeorge wrote:

    The A/C may have \"signed\" for the bird, but if a crew member screws up in doing his job, it\'s not the A/C who\'s name and position are highlighted in the Incident Report or AIB Report as the primary cause.

    I\'ve been in heaps of trouble for things my crew did (mainly LMs :laugh: ). I\'ve been on a AIB & fought hard to keep crew issues from getting planted on a single crewmember\'s shoulders too. The bottom line is, the buck stops with the AC - like I said, there\'s often collateral damage & other crew positions get hit.

    SEFEGeorge wrote:

    Learning how to \"run a panel\" is not the same as operating the panel.

    I know what you\'re saying here, but it isn\'t rocket science (neither is flying the plane for that matter). Familiarity makes it easier & expertise from being the man who does it makes you proficient. I don\'t claim to be proficient & I\'m happy to let the FE run the overhead panel.

    SEFEGeorge wrote:

    When was the last time you put the LM in your seat and had him fly the plane so he could learn your position? When was the last time you did a pre-flight when it was -30 degrees?

    I\'ve done both of those things. I also did my last sim refresher from the FE seat & loved it - I learned a lot. You should never stop learning.

    SEFEGeorge wrote:

    And not to belabor the point if I was administering a flt eval, or for that matter even a regular mission, and a co-pilot or A/C flipped a switch on the FE\'s panel. Then after landing I\'d be talking to my boss about non-qualified crew members operating panels. If you get in to a mindset where you start flipping switches on the FE\'s panel whenever you feel like, are you going to do the same thing during an ASET eval?

    Maybe AFSOC is just different, but yes. If the FE was not able to take care of the panel because he was in back working an issue, checking a leak, or whatever, then I would - even on an ASET eval.

    You keep taking my posts personally & it\'s not my intent. I simply asked why you did what you did & the answer was basically some pilots are arrogant. I still stand by my statement you might have been better off with the tactful approach, but that\'s not everyone\'s style - that\'s fine too.

    It\'d be an awfully boring world if we were all the same...:cheer:

  8. SEFEGeorge wrote:

    Well US Herk, in my years on the Herc I did teach Pilots, Co-Pilots Navs, and even LMs systems. If they had a question I would gladly answer it.

    No doubt - all good engineers do. My point was there\'s a different way to handle it than just pissing him off.

    SEFEGeorge wrote:

    But the point being is that you touch someone else\'s panel without asking or informing first. How\'d you like it if the FE hit the starter button, set your BDHI, tweaked the autopilot servos, moved the flap handle/gear handle, silenced the gear warning horn, etc?

    If he\'s doing it to help, maybe. If he\'s doing it to piss me off, we\'ll talk.

    SEFEGeorge wrote:

    The overhead panel is the FE\'s concern and responsibility. If something happens up there the FE is the one who\'s trained to handle it, and who\'s A** is in a crack if something goes wrong.

    Ultimate responsibility lies with the A-code & it\'s his a** in a crack. Sure, there may be \"collateral damage\" when the A/C gets taken out, but the A/C needs to know how to run that panel & a co-pilot is nothing more than an A/C in training (if he\'s any good).

    SEFEGeorge wrote:

    But I guess that was before the days of Political Correctness. You all may be in the mid-east a lot, but we trained a lot to do just what you\'re doing now.[/

    Yeah, PC BS sucks, but it doesn\'t mean we don\'t have good crews, good training, and get the job done. Good AFSOC crews learn each others crew position...

    The purpose of my original post wasn\'t to start anything - on the contrary. But it seemed the discussion devolved into co-pilot bashing for the sake of co-pilot bashing & a game of one up-manship (I was waiting for the, \'oh yea, I once punched a co-pilot for even looking at my panel!\') - which serves no good purpose.

    Going back to your original post:

    SEFEGeorge wrote:

    There were a few times that I had a pilot or co-pilot reach up to the fuel panel, the air conditioning panel, or the electrical panel. I let it go the 1st time that they did it, but the 2nd time I had my pointer (those extending pointers shaped like a pen), and smacked them across the knuckles. Didn\'t set well with a few, but the ACs realized the no-no, but some of the co-pilots got beligerant and either got put in their place by the AC or by my \"tactful\" approach to their response.

    Why let them get away with it the first time? Why not politely ask them to ask you to do whatever it is, or if they wanted instruction, you\'d be happy to give it to them. Instead, they get the silent treatment the first time implying that it\'s OK just so you can smack them with your pointer when you catch them the next time. Perhaps it\'s me, but I don\'t see how that\'s constructive.

    This is not an attack on you - I\'m just curious why you did things that way?

  9. SEFEGeorge wrote:

    There were a few times that I had a pilot or co-pilot reach up to the fuel panel, the air conditioning panel, or the electrical panel. I let it go the 1st time that they did it, but the 2nd time I had my pointer (those extending pointers shaped like a pen), and smacked them across the knuckles. Didn\'t set well with a few, but the ACs realized the no-no, but some of the co-pilots got beligerant and either got put in their place by the AC or by my \"tactful\" approach to their response.

    Why didn\'t you just teach him about the fuel system instead?

  10. Forward Air Refueling Point or Forward Air Refueling/Rearming Point.

    Think Eagle Claw & Desert 1.

    Land, hook hoses up to the aircraft SPR, & refuel/rearm helicopters. Was used extensively in Afghanistan - particularly the rearming part.

  11. Dan Wilson wrote:

    Bob, by the time I retired the P model did just about everything the E and H model did. Refueling, resupply, airdrops etc.

    Yes. Just not quite as well. :laugh: :kiss:

    We didnt do seizures or FARP (even thought FARP kept raising its ugly head). Besides the only thing they could do that we could not was low level girly style!We didnt have the TFTA to set and forget LOL

    Set & forget...yeah, that\'s how it is. Autopilot too. Cush. Easy. ;)

    Whisky has no TF, no ECM. Has high-speed ramp/door, UARRSI, SOFI-type stuff (FLIR, etc.), 241 radar - but 1 nav. Talon-lite or shado-plus - however you wanna look at it. :laugh:

  12. HeyChief wrote:

    The first 3 then 5 MCW\'s started out as Combat Loss Replacement(CLR), to replace the 4 T2\'s and 1 Shadow AFSOC pranged. They were to be non-operational training aircraft and then be modded and delivered as a post-AMP MCH\'s.

    There was a parallel initiative to provide 10 post AMP MCH\'s (+10 Program).

    OSD set aside 3 C-130H2\'s for CLR and 10 C-130H2\'s for MCH +10 program. The AMP program continued to slow-leak and added to the CWB issue, resulted in a conglomerated program to provide 12 MC-130W\'s to the war fighter as an interim solution. The program of record has these 12 aircraft turning into MCH\'s whenever AMP is figured out. Will we ever see that? Who knows?

    How does 10 +3 = 12? You need to talk to the math geniuses at USSOCCOM.

    At one time, we were hearing a total of 15 aircraft - I know that\'s not in the program of record, but...

    And 10+3=12 to keep people at SOCOM out of jail.

    The MCARS coupling is NATO standard however, the Variable speed drogue (VSD) will not fit into the tunnel of a Sargent Fletcher. (The VSD is rock steady and a monster, the 160th guys love \'em)

    Have heard the positive feedback from 160th before - glad to hear it. Can the SF pod tunnel not be modified to accept it? It would seem that getting the ligher (not by a lot) SF pod & the VSD would be the obvious win/win best COA...or has nobody gone down that road?

    Still - there is no money for J. There is no money for Cannon. There is no money for GSP (which I\'ve heard is officially dead). As I\'ve said before (a quote I stole from someone else) - Leadership \"vision\" without funding is called hallucination. :silly:

  13. That\'s what common sense would say. ;)

    Weight is never looked at until it\'s too late.

    First - I\'m not MCARS qualified. However, I\'ve heard (and I could very well be wrong) that the VSD is retrofittable to any NATO-std coupling. If true, you could hang it on a Sgt Fletcher pod (which FRL owns now). I would assume the hydraulic Sgt Fletcher could reel in the hose/drogue at high speed...but that\'s an assumption.

    Who knows - every bit of the above may be incorrect... ;) ;)

×
×
  • Create New...