On the CSVs with velocity, make sure you specify the coordinate system, particularly whether it is inertial (J2000 or MME) or rotates with Mars (IAU_MARS). This is the difference between inertial velocity and airspeed (discounting wind). To get geodetic latitude, longitude and altitude, use IAU_MARS coordinates and run it through the code described here (fortran, but short and easy to translate) http://www.astro.uni.torun.pl/~kb/Papers/geod/Geod-BG.htm
. The ellipsoid used with this spice kernel is a=3396.19km, b=3376.20km, centered on Mars center of mass, b axis=polar axis
Once you have the geodetic latitude and longitude, you can set up a local vertical coordinate system at each point and convert airspeed into north, east, up coordinates. Also, from the inertial velocity, you can do a numerical differentiation (acceleration=change in velocity/change in time) which is what I did to get the parachute graph above. You know the distance to the center of Mars and can therefore subtract off gravity and you are then left with non-gravitational accelerations generated by such things as drag, lift, engines, and resting on the ground. This non-gravitational acceleration is what the accelerometers feel. Also since you know the inertial velocity it is possible to set up a lift/drag local coordinate frame at each point to get lift and drag acceleration. With the inertial attitude provided by the attitude kernel, you can get angle of attack in both directions (and confirm that the entry vehicle is not spinning) and with the mass of the vehicle, you can get lift and drag force as a function of velocity and angle of attack along the entry corridor. You still need a Mars model atmosphere to get all the way to Cd and Cl, and this cannot be derived solely from the kernels.
So yeah, this data is enough to do some interesting aero models.
Event times, based on acceleration transients in most cases
Time from start of SPICE kernel, Event
0, SPICE kernel starts, 2008 May 25 23:30:57.920 UTC SCET, 3522.2km from center of Mars, (Entry interface, 125km above spherical reference surface)
15.202, 125km above ellipsoid (23:31:13.122 UTC SCET) (Interpolated)
122.955, Peak deceleration, 84.2403m/s^2
227.825, parachute firing
228.935, first peak parachute deceleration, 82.962m/s^2
242.825, heat shield jettison
252.985, leg deploy
253.485, leg deploy
253.980, leg deploy
404.940, lander separation
405.516, First thruster pulse, low thrust
408.005, First thruster pulse, high thrust
429, transition to constant velocity
431, constant velocity achieved, ~2.65m/s down
446.005, peak of touchdown transient, 52.666m/s^2, 23:38:23.925 UTC SCET, 430.804s after entry interface
452.860, SPICE kernel ends, 2008 May 25 23:38:30.780 UTC SCET
Edit: Entry interface is 125km above a spherical Mars reference surface, or 3522.2km from the center of Mars. I originally had entry interface 125km above ellipsoidal surface. It turns out that the spice kernel starts within 5ms of entry interface as properly defined. It is obvious that the kernel is intended to start exactly at entry interface.