JERICHO Level 1 flight with telemetry overlay

Nov 09, 2026 Last reply: 1 hour ago 3 Replies
Jump to replies (3)

The number that jumped out at me is the speed: 646.2 miles per hour just 1.35 seconds off the pad, on an H motor. That is a serious punch for a Level 1 flight, and having the altitude count up on screen alongside it makes the figure land even harder. Apogee came in at 2,398 feet at 10.65 seconds.



The rocket, named JERICHO, was on its second flight, and this time the maker added onboard GPS, a flight computer, and a camera. RedSensei flew it on a CTI H143, with electronic deployment at nose over and a Rotofoil 30 inch main parachute for recovery. Flight data came from an Eggtimer TRS using filtered altimeter readings, while the footage was recorded with an 808 camera mounted on the side of the airframe. To build the overlay, the maker used DashWare, one of the few programs that would read video from that camera.



Plenty stands out here. The airframe wears a gold ogive nose cone and a red body tube, which reads as a clean color scheme. The overlay tracks flight time, speed in miles per hour, and altitude in feet, and the whole flight lasted 129.65 seconds before the rocket settled upright in a grassy field. Descent under the chute ran roughly 13 to 16 miles per hour downward while the rocket spun, with the launch site, ponds, fields, and vehicles passing below. The launch happened with the Tripoli Tampa Rocket Association at Plant City, supported by a pad, a rail launcher, and a ground station box with antennas and indicator beacons.



One open item: no serial logger was attached, so the GPS data was lost. In my view that is the obvious gap to close on a future flight, since the GPS hardware itself was already along for the ride.



Project by RedSensei. Watch it on their YouTube channel:

formatting link


Picking DashWare strikes me as clever problem solving. With so few programs that would read video from the 808 camera, settling on one that actually works saved the whole overlay idea. I also think leaning on filtered altimeter data from the Eggtimer TRS was the right call, since filtered numbers tend to make a cleaner on-screen readout than raw ones would.

How was the 808 camera attached to the side of the airframe? I keep wondering whether it sat flush against the body tube or on some kind of stand-off, and whether the mounting held steady through that 646.2 mile per hour peak without shifting the view on the way down.

For the next flight I would add a serial logger to capture the GPS stream. The GPS and flight computer were already flying on JERICHO, so logging that output would turn the lost track from this flight into a full recorded flight path next time. It would also give a second dataset to compare against the altimeter readings.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required