Congress approved Lorna’s Law on May 4, 2047, sending to the president a commercial-drone safety package written after a delivery aircraft crashed into a Boise playground and killed eight-year-old Lorna Reynolds.
The accident had become a national test of how existing aviation rules applied to rapidly expanding autonomous delivery networks. Commercial carriers were flying millions of low-altitude routes through populated areas, often with highly automated dispatch, routing, collision avoidance, and fleet management. The Boise crash forced regulators and lawmakers to examine whether approval standards had kept pace with the scale of deployment.
What the Law Changes
Lorna’s Law establishes a higher federal threshold for commercial delivery-drone operations over populated areas. Operators can no longer treat dense residential and public spaces as an ordinary extension of lower-risk routes. FAA approval is required before qualifying delivery operations can use those areas.
The law also strengthens incident reporting, route records, operating restrictions, and responsibility for the companies deploying the aircraft. The central premise is that autonomy does not sever the line between a machine’s decision and the organization that authorized the system to operate.
Carriers remain able to use autonomous delivery where they can meet the standard. Some routes will require different equipment, greater redundancy, revised corridors, or additional human supervision. Other routes may no longer make financial sense.
The Boise Investigation
Investigators examined the aircraft, routing system, fleet software, maintenance history, communications records, and operational decisions leading to the crash. The case drew attention because no single dramatic mechanical failure explained every question raised by the flight.
Chastain argued that a safety regime built around assigning blame after an accident was inadequate for systems making thousands of automated decisions before a human operator could intervene. The approval process had to examine the full operating system, including how the aircraft was routed, monitored, updated, and removed from service when risk increased.
Her office also resisted proposals that would have treated compliance with an industry performance average as a complete defense. Aggregate safety statistics remain important, Chastain said, but a company still has a duty to operate safely in the particular environment where it deploys the system.
The Cost Argument
Delivery companies warned that the legislation could eliminate marginal routes and reduce the economic advantage of autonomous delivery. Chastain acknowledged that possibility during negotiations.
Her position was that a business model should include the cost of meeting the safety standard for the environment in which it operates. If a route only remained profitable by using a risk tolerance Congress considered unacceptable around homes, schools, parks, and crowded public spaces, the route could not claim an entitlement to continue unchanged.
The legislation therefore avoids a nationwide prohibition. It creates a stricter operating gate for populated areas and leaves companies free to redesign their systems around it.
Why the FAA Remains Central
Congress did not attempt to write aircraft engineering specifications line by line. The FAA remains responsible for technical approval, operating conditions, certification, and enforcement within the authority created by the law.
That distinction mattered to engineers who testified during drafting. Aircraft, sensors, software, communications, and operational concepts change faster than statutory text. Congress established the safety threshold and accountability structure. The aviation regulator retains the technical job of determining whether an operator has met it.
A Broader Technology Principle
Lorna’s Law became Chastain’s first nationally visible technology-accountability fight after her election to the Senate in 2044. It also reflected ideas she had already used in Idaho policy.
Technology could create enormous economic value. The company deploying it remained responsible for physical consequences. Safety rules had to be specific enough for engineers to design against. Public officials had to retain meaningful authority over systems operating in public space.
Those principles would later appear in other areas of Chastain’s work, from quantum-core security to algorithmic systems. In 2047, the argument was narrower and painfully concrete: an autonomous delivery network operating above a city still had to answer to the people living beneath it.