Hi, first post. I've been working in automotive powertrain controls for 9+ years now, first for an ECM supplier, Visteon, and now for GM Powertrain. My area is diagnostics calibration, so I've troubleshot just about every piece of an engine management system that can go wrong. Even in a simple system (engine only, no transmission), I wouldn't really trust flying in an ECU-equipped light plane with an automotive motor unless there was almost two of every key control component. Dual plugs, dual ECUs with fully independent power supplies, etc. Preferably dual engines...
Automotive ECUs are very durable, designed to operate -40 F to 150F, for 150000 miles. But the airplane 'drive cycle' is so different than a car, there's just too many unknown failure modes out there that can bite you. Temperature gradients for one, sustained high output from the output drivers on the circuit board, power supply fluctuations, etc. One obvious area is altitude compensation. Most automotive baro tables are limited to 12,000 feet, which is basically the highest road in the world. Anything above that is all error buildup.
The most aggravating issues to solve are the one-off cases that come out of nowhere; where it took a perfect alignment of multiple factors to reveal the issue. The thing is, no matter how robust the calibration and validation is, there's always one fault mode out there that doesn't show itself during development, no matter how many hours on the dyno, test vehicle miles, or development trip hours you have.
I'm glad to see yet another application of the venerable small block Chevy, though.
Rob Weiss