A week on the bench moves in airflow, not in folders
Every engagement at BAV Technologies LLC runs along the same measured lanes. We do not hand a client a spreadsheet and wish them luck. We walk the envelope through six instrumented stations, and each station leaves a record that the next station reads before it starts. The rows below are the running order of a typical bench week.
-
Lane One
Float Bay Desk
The float bay desk is where an envelope first earns its sheet. We log the gore count, seam pattern and gross lift target, then reconcile those figures against the gas cylinder weight tags before the canopy is ever inflated on the floor. A clean float bay sheet is the gate that admits the envelope to the rest of the bench.
-
Lane Two
Wind Lane Rounds
Wind lane rounds move the inflated canopy through a controlled drafting corridor while wall-mounted pressure taps map how the envelope sheds crosswind. Our control software samples every tap on a fixed cadence, and the operator writes a round note at each pass so a later engineer can replay the exact gust sequence.
-
Lane Three
Valve Weeks
Valve weeks are dedicated to the relief and dump valves that keep an envelope from over-pressurising. We cycle each valve against a calibrated reference, record crack pressure across a sweep of temperatures, and rebuild any valve that drifts outside its band. The finished week closes with a labelled valve set and a tolerance card set for the flight crew.
-
Lane Four
Ballast Days
Ballast days test the sand sacks and release lines that give a pilot trim authority. We weigh every sack on a certified balance, hang the release ring on the bench gantry, and time the drop sequence across repeated pulls. The goal is a ballast set that behaves the same in a cold morning shed as it does at altitude.
-
Lane Five
Burner Check Sessions
Burner check sessions measure flame stability, fuel draw and heat output against a load cell rig. We log the burner through warm-up, cruise and cold shutdown, capturing any pressure sag that could turn a smooth climb into a lurch. Each session ends with a rebuilt fuel line spec and a chart the crew can read at a glance.
-
Lane Six
Tether Run Evenings
Tether run evenings prove the whole stack together. The envelope is tied to our ground ring, the burner is lit, ballast is loaded and the integrated control software logs the entire run as one timeline. We finish each evening with a signed tether record that documents every input the crew touched and every sensor that answered.
Why a bench beats a spreadsheet
Hot gas envelopes fail quietly. A seam that is two millimetres short, a valve that cracks late, a burner that sags under load, none of these announce themselves in a spreadsheet. They only show up when a measured rig refuses to lie. BAV Technologies LLC was founded on that premise, that a system is only as trustworthy as the bench that signed it off.
Our Logan workshop at 155 W 800 N, Logan - 84321-3215, United States (US) holds the float bay, the drafting corridor, the valve cell and the tether ring under one roof. Because every station feeds the same control software, a test that starts at the float bay desk is still traceable when the envelope is on the tether ring weeks later. We call that a single thread, and it is the core promise of our bench.
We are a computer systems design firm first. The industrial software that samples pressure taps, drives valve sweeps and logs burner output is written in house, against the specific sensor stack each client brings. That is why our engagements look less like a checklist and more like a small engineering programme with a clear start and a clear release sheet at the end.
- Instrumented pressure taps on every gore, sampled on a shared clock.
- Valve crack pressure tracked across a full temperature sweep, not a single point.
- Burner output logged through warm-up, cruise and cold shutdown.
- Ballast weighed on a certified balance and drop timed on the gantry.
- Tether runs recorded as one integrated timeline, signed and archived.
- Release sheets written for a crew that reads them in a cold morning shed.
Our tether window opens each morning once the bench lead reads the float bay sheet aloud and closes the fuel line, so every evening run starts from a known, documented state.
How we work with integrated systems
Design before metal
We begin every engagement by mapping the sensor stack, the control loop and the operator interface before a single bracket is cut. A float bay gantry that cannot report its own load is a liability, and we will not build one. The design phase produces a wiring schedule, a sampling plan and a release criteria document that the client signs before the bench is touched.
Software that fits the rig
Our engineers write the logging, sampling and alarm software against the specific hardware in the workshop, not a generic dashboard. That means a pressure tap can be re-zeroed with two clicks, a valve sweep can be paused mid-pass, and a tether run can be exported as one timeline. The software is the quiet half of the bench, and it is where most of our effort lands.
Records a crew can trust
Every station we run hands off a physical sheet: a float bay log, a wind lane round note, a valve tolerance card, a ballast weigh sheet, a burner chart, a tether record. We build these sheets to be read under poor light by tired hands, which means large figures, clear bands and no clever abbreviations. If a crew cannot read the sheet, we have not finished the job.
What a full bench cycle actually looks like
A typical cycle runs across three bench weeks, and the order of the stations matters as much as the stations themselves. We start with the envelope, because a canopy that cannot hold pressure will not survive a wind lane pass, and we finish with the tether run, because an integrated run proves every earlier note at once.
-
Stage One
Envelope intake and float bay reconciliation
The first stage is paperwork meeting fabric. We reconcile the gore count against the build sheet, weigh the empty envelope, and record the seam pattern from photographs taken under a fixed lamp. Any mismatch between the build sheet and the fabric stops the cycle before inflation, because a float bay that starts on a wrong assumption produces a wind lane round that means nothing.
The reconciliation note travels with the envelope for the rest of the cycle. By the time the tether run closes, a reader can trace every measurement back to the intake figures.
-
Stage Two
Inflation, drafting and wind lane rounds
Once reconciled, the envelope is inflated under the drafting corridor and the pressure taps come online. We run at least four rounds per lane, each at a different fan speed, and the control software stamps every tap sample with the round number. A round note records the operator, the ambient temperature and any tap that drifted during the pass.
We do not smooth the data at this stage. Raw samples go into the record, because a pressure spike that a later engineer needs to explain must survive the first pass without being averaged away.
-
Stage Three
Valve weeks and ballast days interleave
While the envelope rests between lanes, the valve cell cycles the relief and dump valves against the reference rig, and the ballast bench weighs and drops the sack set. These two stations interleave because both depend on the same temperature log, so a cold morning valve sweep can be compared directly with a cold morning ballast drop.
By the end of this stage a client holds a valve tolerance card and a ballast weigh sheet, both signed, both written for the flight crew rather than for an archive cabinet.
-
Stage Four
Burner sessions and the integrated tether run
The burner check sessions come last because they produce heat that would distort the envelope measurements if run earlier. We log the burner through warm-up, cruise and shutdown, then hand the rebuilt fuel spec to the tether evening, where the whole stack finally operates together.
A tether evening closes the cycle. The envelope is tied to the ground ring, the burner is lit, ballast is loaded and the control software records one timeline across all stations. The signed tether record is the document a crew takes to the field.