i Pod Shot g un
Engineered with precision, executed with near-perfect reliability — and still amounting to nothing. On cars that jump over other cars.
Adevice can be engineered with precision, controlled by software, and executed with near-perfect reliability and still amount to nothing more than an iPod shotgun: a consumer object whose form factor has been fused with a capability that has no ordinary use. The phrase is not an argument against technical achievement. It is an observation about the gap between what a machine can do and what the surrounding order of use, law, and expectation is prepared to treat as normal. In the case of a vehicle system that calculates and performs a jump over other cars, the gap is the entire point.
An iPod, in its original commercial life, was a portable device for storing and playing music. It solved a defined problem of personal audio. Its success did not come from technical novelty alone; portable music players existed before it. It came from fitting cleanly into habits people already had: commuting, exercising, listening alone in public. The device asked nothing of anyone except its owner. A shotgun is a firearm whose ordinary purposes, whether hunting, sport, or defense, are already governed by separate regimes of licensing, storage, and use. Those regimes exist because a shotgun’s effects do not stay with its owner. They extend to everyone within range.
Nobody’s listening is enhanced by a barrel, and nobody’s hunting is improved by a click wheel.
Mating the two produces an object that retains the interface of one and the destructive potential of the other while inheriting the legitimate purpose of neither. The result is not an improved music player and not a more convenient firearm. Nobody’s listening is enhanced by a barrel, and nobody’s hunting is improved by a click wheel. It is a novelty whose primary demonstration value is that the combination is possible. Once the demonstration is complete, the object has nowhere ordinary to go. It can sit in a collection, appear in a video, or be fired at a range under the rules that already govern firearms. What it cannot do is migrate into the pocket of the ordinary commuter, because the category it would need to enter, personal audio, has no place for the thing it adds.
The same structure appears when a motor vehicle is given the capacity to leave the roadway and clear other vehicles by calculation and thruster. Consider the actual history of driving automation. Anti-lock braking modulated pressure the driver was already applying. Cruise control held a speed the driver had already chosen. Parallel parking assistance, adaptive cruise control, and lane centering automated tasks that drivers already performed, or reduced the frequency of ordinary errors in performing them. Each remained inside the category of surface operation on public roads. Each made the vehicle behave more like a careful driver, not less. Their gradual acceptance followed from that continuity: the act was already lawful, the risk profile was familiar, and the utility was immediate. A regulator evaluating automatic emergency braking was not asked to decide whether stopping is a legitimate thing for a car to do. It was asked only whether the machine stops better than the person.
A system that computes a trajectory, fires thrusters, and lands beyond a line of cars does not continue that sequence. It is not a better version of anything drivers already do. No driver, however skilled, performs the maneuver it automates, because the maneuver was never part of driving. It substitutes a different category of movement, one closer to flight than to traffic, whose ordinary purpose on a public road has not been established. The question it raises is not whether the machine jumps better than a person. It is whether jumping is something a car on a public road should do at all, and that question has no precedent in the history of automation to lean on.
Reliability does not close the gap. A system that succeeds ten times out of ten in controlled conditions has demonstrated engineering competence. It has not demonstrated that the maneuver belongs among the expected operations of traffic. Controlled conditions are, by definition, the ones the engineers chose. Public roads supply the ones they did not: a child stepping between parked cars, a truck taller than the sensors assumed, a gust of wind, a vehicle that brakes during the ascent, a pedestrian on the far side of the landing zone. Ten successes say little about the thousandth attempt, and nothing about the consequences when it fails. A failed parallel park produces a scratched bumper. A failed overflight produces a vehicle descending onto other people’s roofs.
More fundamentally, traffic is a coordination system built on mutual prediction. Every driver, cyclist, and pedestrian moves on the assumption that other vehicles will stay on the surface, travel within lanes, and change position at speeds and in directions that can be anticipated. That shared expectation is what allows strangers to pass within feet of each other at highway speed. A vehicle that may at any moment rise over the cars around it breaks the assumption for everyone nearby, whether or not the jump succeeds. The other road users did not choose the maneuver, cannot anticipate it, and have no way to respond to it. They simply absorb its risk.
No exception for perfect execution.
The statutes that prohibit reckless driving and unsafe vehicle operation reflect exactly this. They do not contain an exception for perfect execution. They address the decision to create a hazard that other road users must absorb, whether or not the hazard materializes in any given instance. A driver who weaves through traffic at high speed without striking anyone has still driven recklessly. The offense lies in the imposition of risk, not in the collision. Automation changes the source of the inputs; it does not change the character of the act. The operator who engages the system remains the operator of a motor vehicle. The fact that software calculates the angle does not convert an overflight into parking, any more than a rangefinder converts a gunshot into a measurement.
“The offense lies in the imposition of risk, not in the collision.”
Regulatory language already registers the distinction. Versions of the vehicle equipped for the maneuver are labeled as not approved for public-road use, or as oriented toward track or air applications. That labeling is not a marketing flourish. It mirrors a familiar pattern: race cars without road certification, off-road vehicles barred from highways, experimental aircraft confined to designated airspace and conditions. In each case the machine is lawful to own and lawful to operate, but only in a setting where its risks fall on people who have accepted them. The label is a recognition that the capability lacks the ordinary utility that would allow it to travel the path taken by automated parking.
Without that utility, the system remains specialized equipment. Specialized equipment can be owned, demonstrated on private property, and restricted on public roads by the same mechanisms that already limit other high-risk vehicle behaviors. The restriction does not require a new statute written for thrusters. Existing rules against operating a vehicle in a manner that shows willful disregard for the safety of others are sufficient once the act is observed. A police officer does not need a thruster code to recognize that a car flying over an intersection has departed from the expected conduct of traffic. The law does not have to anticipate every new way of creating danger. It only has to describe danger well enough to recognize it when it arrives.
Time and technology do alter what counts as normal. Seat belts went from optional accessory to legal requirement. Right turns on red went from prohibited to routine. Consumer drones went from unregulated toys to registered aircraft with altitude limits and no-fly zones. Electric scooters went from sidewalk nuisances to permitted fleets with designated lanes. None of these shifts happened because the technology simply worked. They happened through the intermediate step of redefinition: new standards, explicit permissions, or accumulated practice under conditions that regulators have accepted. Someone had to argue that the new behavior served an ordinary purpose, define where and how it could occur, and assign responsibility when it went wrong. Only then did the behavior move from novelty to category.
Until that redefinition occurs, capability alone does not update the category. A vehicle that can clear a line of traffic has not thereby earned a place in traffic, just as a drone that can fly over a stadium has not thereby earned the right to. The burden lies with the capability to establish its purpose, not with the existing order to make room for it.
An iPod shotgun can be built to high tolerances and controlled by elegant software. It remains an iPod shotgun until someone establishes a use for it that the existing order of music players or firearms is prepared to absorb. The same holds for a car that can calculate a jump. The engineering may be real.
