HerkPerfMan

People and politics are always the biggest obstacles. It also seems that the various USAF commands (AMC, AFRC, AETC, AFSOC, etc.) do not have a unified strategy for adopting EFBs; everyone is seeking their own solutions. Is AMC actively working on an e-told app for the KC-10 or any other tanker/airlift systems? I know there are weight-and-balance (form f) apps for some platforms but I haven't heard about any e-told or other performance calculation apps.

It sounds like the iPads are essentially being used as e-readers at this point. Hopefully USAF recognizes the potential of them as a comprehensive EFB once the configuration control and distribution infrastructure matures. They are very popular in the general aviation community and have been adopted by some major airlines. Though I saw Delta opted for the new Microsoft Surface. AMC has been experimenting with the mini on the C-21, at least. http://www.bnd.com/2013/07/07/2686018/goodbye-paper-maps-and-charts.html

The initial version of our C-130J TOLD calculator (preTOLD) is designed to run on Windows-based laptops and tablets, but we are also working on an iPad version. I've been reading a lot lately about the adoption of iPads within USAF and am curious about the user experience so far. How are they being utilized so far and what is the state of the configuration/app distribution infrastructure? What sort of flight planning applications are available? Are other services also planning to adopt iPads for flight planning?

Thanks for the heads up, I hadn't even considered whether I could use the name, though I'm certainly not the only one using the military designations. LM has some interesting ideas about what it does and does not own...

Is the SIB or complete AIB report available to the public anywhere? Having only read the exec summary, it doesn't sound like a brake energy problem but rather a ground roll problem. They probably didn't plan to land 27 knots high (you couldn't plan for that if you wanted to) or touch down 1500 ft down a high altitude, 6900 ft runway, but both would have significantly impacted any ground roll distance margin they may have had. Glad everyone made it out ok.

Yes, and our company is registered with DDTC. We are currently targeting the US market, but a Letter of Intent from a foreign customer and access to their tech pubs would allow us to apply for an Export License.

We're starting with the J and plan to work on the H next, if we get some traction. Brake energy data are included for landing and we are exploring the addition of a tool to calculate brake energy for aborts and quickturns. I don't know why a Brake Temperature Monitoring System (BTMS) wasn't added to the J; it is not new technology and would certainly reduce the 60-minute minimum cooling times. Also, we have incorporated fixes for the mitigations currently required for Block 6.0. Indeed, these are both big issues we are currently tackling. Definitely some gray areas and I'm just an engineer but here is my take: The software and methodology (the "math") that Lockheed uses to develop the performance charts (-1-1) are proprietary, but I don't need that. I only need the resulting scheduled data/printed charts. Again, Lockheed owns the copyright but operators (USAF, USMC, USCG) can release their publications to other contractors. Another thing worth noting is that the definition and structure of flight manual data is governed by DOD standards/regulations which are publicly available (MIL-DTL-7700, MIL-STD-3013). I'm no lawyer, just a lowly engineer, but I think any OEM would have a tough time asserting ownership over methods and procedures that are "industry standard" and in the public domain. As for liability: On the J, the Mission Computer (MC) currently hosts a DO-178 Level A-certified version of TOLD which we are not trying to replace. We are solving the problem of accessibility by providing "advisory data." Our goal is to make preTOLD as close to MC TOLD as possible, but in the event of a conflict, MC TOLD is still gospel. Definitely some gray areas but, needless to say, I'm working several angles on this.

For the past few months, I have been developing a PC-based Takeoff and Landing Data (TOLD) calculator for the C-130, with an iPad version also in the works. We call it "preTOLD" and you can find more information, including current features and screenshots, at our website: http://www.elitetest...e-and-services/ At this point, we have a prototype completed for the C-130J and are seeking feedback from the pilot and mission planning community on the user interface design and functionality. Specifically, I'm interested to know which features are essential and who would use them, but any other insights are certainly welcome. We are also offering a pilot training course covering the finer points of TOLD planning and the associated performance data to enhance situational awareness and improve flight safety. Please take a look around the website and reply with any comments, questions, or criticisms. PM works too and my email is listed on the website along with details of my C-130 background. Thanks, Kevin H.