Why don't you develop a protocol, then some of us can duplicate your experiment and provide data for your research.  I'm always looking for a reason to fly . . .  I hate just boring holes in the sky.

 

Moondog,

 

OK. For a 235/320/360:

 

1.  Equipment description: engine?, pistons/compression ratio?, Induction air (Ram?, filtered?)?,  Ignition?, Fuel - O, IO, TIO or blown, special "features", AP with altitude hold? engine/airspeed instrumentation?  Quality GPS with possibility of Km per hour? Static Air source?  Maybe we can build a tester's database? Was Airspeed indicator calibrated? Gross Weight and CG.

 

2. Before engine start,

Baro reading, MAP reading, OAT, Dew Point

 

3. Test Cruise Altitude - good cruise altitudes are 6500/7500 (~= 75% power), 8500/9500 (design altitude), 11500/12500 (good x-ctry altitude).

Altitude, Baro, OAT, KIAS (If RMI, Palt, Dalt, TAT, KTAS - Otherwise compute on E6B or spreadsheet to be developed), w or w/o AP alt hold engaged.  Also, report any turbulence.

 

WOT (unless testing MAP), MAP, RPM, gph (leaned for best power, 100* ROP?), optionally CHTs and EGTs.  If altitude change, relean to same EGT is OK.

 

Can you think of more data?  Chris suggesting also calibrating MAP sensor (maybe I can think of a way to do that with a spare altimeter).

 

CAS can be computed from TAS if you've got a good GPS.  Most update every second, the new WAAS capable update many times a second and are extremely accurate.