Jump to content
Baseops Forums


Registered User
  • Content Count

  • Joined

  • Last visited

Community Reputation

15 Good

About Torch09

  • Rank

Contact Methods

  • Website URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Torch09

    What is next for the UPT-Next graduates?

    We've been directed to AR in Bronco a few times to justify it's existence. There's a B-21s-at-Dyess incentive plan to bridge Bronco and Lancer, add in some Link-16 infrastructure all the way out to Pecos, and make a super-MOA. They call it the Raider MOA...keen.
  2. I received my AZ absentee ballot: Vindictive careerist (R) Commie lunatic (D) Sonuva beech
  3. Torch09

    What is next for the UPT-Next graduates?

    Lancer is surprisingly busy: 90% Bones, the rest from BUFFs (KBAD), Vipers (NFW), C-130s, and the occasional F-35 (Lockheed plant, DFW). IR-128, while flat and soul-less, starts and ends in Lancer for a hip-pocket LOWAT rehack. Snyder is a pretty good EA site, used and abused by all 5 squadrons at Dyess. Adding some AETC traffic is possible, but not ideal.
  4. Torch09

    RFI on aircraft systems

    Excellent, I shall add it to the data gonkulator.
  5. Torch09

    RFI on aircraft systems

    Shucks, you caught me. I figure if I know all the systems of all the things, my T-6 Flt CC will boost my class rank. It's that or bang a FAIP, right? It's the early stages of a developing "What's wrong with the AF" rant. To look beyond the sport bitching amongst the bros and see what risks we're actually taking with certain systems inop, a comparison with other MWSs would help. Create your own template, with blackjack and hookers.
  6. Torch09

    RFI on aircraft systems

    Requesting data from airframes across the inventory to build up a comparison of how different aircraft handle major emergencies. Primary flight control systems + any backups: To include backup hydro sources, mechanical backups to the primary, combinations of hydro/electric redundancy. How they handle engine-out and/or hydro-out situations: How serious is losing all or most of those systems? Is it time to punch out, or do you have options to still recover those systems? Partially exposed gear that can work without full extension (giggity), practical air-start procedures, windmilling motors that provide sufficient hydro px to land. The ability to land after losing those systems: Is it still controllable, and will the approach speed/landing roll/flight characteristics/gear configuration let you land on something shorter than a big strategic runway? Other emergency-use systems that enable recovery of the aircraft or aircrew: Backpack parachutes stowed in the back, jettison hatches that don't immediately dump you into a nacelle while airborne, VTOL/ability to land nearly anywhere. Historical risks: Compared to your experience with (or perception of) other aircraft, how likely/frequently do you expect to lose a major aircraft system? Does it mean a high chance of total loss of the aircraft or aircrew? Can be anecdotal or your best WAG on data. Examples, the best I can remember them: T-6 Flight Controls: Mechanical, no backup. Engine/hydro out: Backup hydro reservoir lowers gear/flaps. Mechanical flight controls unaffected. Engine out flight characteristics/landing: Decent glide profile/ELP option (students need not apply). No set minimum runway length for a forced landing, but ROT is ~3000ft. Can always punch out if it doesn't work. As a last resort, the wingspan/landing roll/gross weight/landing gear footprint would enable a landing on most larger roads; it's an option with an engine fire/FOD/frozen and ejection seat failure combo. Other: Martin Baker 0/0 goodness. Historical risk: Low. Very simple and reliable engine, hydraulics, and flight controls. Considering how much AETC beats them up, and with improvements to the PT-6 propeller shaft (eliminating PSTD issues), it’s a safe jet. OBOGS or catching a sleeve on the CFS handle is a separate issue. T-38 Flight controls: Hydraulic, no backup. Engine/hydro out: Windmilling engines at normal cruise speeds provide enough hydro px to sustain aircraft control, but not when slowing down for a landing; the jet will depart at some point. If hydro pumps fail/px is completely lost, punch. Engine out characteristics/landing: Dual failure = attempt restart or punch. Restart requires Boldface actions plus sufficient airspeed/altitude. Single failure = recoverable as is. 8,000ft runway is AFI minimum, unknown on IP-recommended real mins if ejection isn’t an option. Other: Various generations of ejection seats, latest is a Martin Baker 0/0. Historical risks: Low-Medium. Old airframe with unforgiving flight control authority when slow. Mechanical issues in the pattern can quickly turn ugly; rudder hardover at Columbus, dual hydro failure at Laughlin, original seats were marginal at pattern altitudes, etc. Template Flight controls: Engine/hydro out: Engine out characteristics/landing: Other: Historical risks: Much appreciated!
  7. I got a little bored. Data for those considering a join spouse relationship: Of the 6.4yrs/2,352 days my wife and I have been married, 2.5yrs/909 days have been apart. That's an average of 4.7mo/141 days per year physically separated by TDY, PCS, or deployment. The average duration of separation is 37 days, including the occasional 1-2 day jet-swap TDYs. We've had one PCS separation that left an 11mo gap, with the rest stationed together. Days apart does not consider leave taken to visit each other while separated via PCS. We also have jobs that are highly compatible, both ops-focused and relatively easy to station together. If we were committed to different MWS's or didn't have today's friendly AF policy directing join spouse assignments, it would be far worse. The 1-3wk TDYs aren't bad. It's enough time for the spouse still home to work on house projects, hog all the time with the kiddos, and then appreciate the return of the TDY spouse. Deployments longer than a couple months suck; 5-6mo are standard in our jobs. Thankfully, we've had CC's on our side for the couple times we've asked for a break. One was simultaneous deployments, leaving our 1yr old with family. The other was staggered deployments, with only 5wks together over the course of 2yrs. CC involvement in both cases helped shift things around, and both worked out well for our family. Things that helped make the separations easier: 1. Set expectations low. Even if it's an easy TDY, walk into each one as though you won't have time to talk until you're both home. Any contact is then a pleasant surprise. 2. Block off leave and family time for after the TDY/deployment well in advance. Keep it sacred. 3. If the AF is paying you to go to Nellis, find a reliable babysitter (i.e. grandparents) for the kiddos and fly the wife out there for one of the weekends. Second honeymoon. 4. Don't overcommit on unnecessary projects. You're both making a decent paycheck, so don't go full dad mode and install a deck by yourself at the expense of relaxing with the family. Pay for the labor on tasks that you don't inherently enjoy, and consider it an investment in mitigating the stress of future time apart. 5. Enjoy the crap out of the times you get the kiddos to yourself. It's a lot of work on top of your day job, but good grief it's fun. 6. Your Family Care Plan forces this, but it's a good idea regardless: Have 2-3 close friends in the local area that you trust to pick up your kids and care for them overnight. I had to ask for help a couple times that a night sortie was unavoidable. Work with DOS to ensure you have as much of a nuggets' up as possible on sorties that will impact your ability to pick up kids from daycare.
  8. Torch09

    USMC F-35B Crash in

    Posted yes, but details are slim: http://www.flyingsquadron.com/forums/topic/22416-usmc-f-35-crash-in-south-carolina/
  9. Torch09

    UPT prep flying with private instructor

    Juice/squeeze = negligible. The vast majority of UPT students walk into IFS/UPT with very little or no experience. Some of the best students I had were CFIIs, but they paid for hundreds of hours of training and then were getting paid to teach others; it's not something you do on your own without a significant financial investment. A couple of the worst students I had were also CFIIs, who had a slew of bad habits and a shitty attitude. Be a bro, study hard, and let the AF pay you for all the training you need.
  10. Torch09

    Gun Talk

    Specifically, enough distance for Sandy to mow down shitheads around you just before Jolly drops in. The effective range of the GAU-5A (considering barrel length, twist rate/bullet stabilization, muzzle velocity, ammo specs) was carefully compared to 'distance' data from friendly weapons to set a minimum threshold. The max was limited by available space in the seat kit. We sent a weapons SME and AFE tech to a conference a few months back to ensure the GAU hit all those requirements. I'm only familiar with what one MDS had to give up in the seat kit to fit the GAU, but given the ground picture in CENTCOM I'll gladly take the GAU over those other niceties.
  11. Torch09

    Gun Talk

    Galil Ace Pistol +brace isn't a new model, but just got it yesterday. Probably the smoothest-cycling bolt I've ever felt (sts). Helluva truck gun: https://iwi.us/product/gap39iisb/
  12. Torch09

    Gun Talk

  13. Torch09

    Flight Scheduling

    I'm not in DOS, I just bitch about the product. How did you learn how to use all the PEX functions? In-house SME? The 1wk training course? Add: a PEX guide or gouge floating around? To clarify: We tried using PEX for everything...entering commitments, tracking currencies, real-time updates displayed on a big screen as the executing scheduler threw 'pucks', etc. The primary drawbacks were: 1. Visualizing commitments and people available vs. lines to fill. Physical pucks or Excel perform this function in a far cleaner format. Even the attached flyers take the time to ensure those two methods of commitments are accurate, vice battling the daily PEX server meltdown. I have 4 hyperlinks to PEX bookmarked... 2. Constant inaccuracies in aircrew currencies. I would show green in ARMS and whatever other program the HARM shop uses, but show red in PEX even after HARM/SARM tried updating it. Additional issue that drove DOT to create a separate RAP tracker: Aircrew would log MARs, sometimes 2-3x, and PEX wouldn't save it. I never had faith our RAP reports were accurate reflections of training accomplished, even assuming a 100% MAR completion rate from aircrew.
  14. Torch09

    Flight Scheduling

    We just moved from a magnetic puck board to a combo of homegrown Excel and PEX. PM me an address and I can ship you a metric shitload of pucks, complete with aircrew names dating back several PCS cycles. The pucks I've seen in AETC and AFGSC both arrived on a reel and you cut them to size, if that helps you order them.
  15. Torch09

    WTF? (**NSFW**)

    A Snickers bar is not the instrument with which I, and most of the rest of America, will ultimately hold our government accountable to the Constitution. There is zero parallel to a child's lack of self-control and foresight on their future health. But to entertain your argument: Name a specific individual, and present medical and/or otherwise convincing evidence to a judge, showing that said individual is a specific violent threat to other human beings, so much so that the government is charged with stripping them of a primary Constitutional right, and I'll stand with you every time. Until you can do that, 'Murica.