-
Five research milestones rebuilt the same two-hour cache: now it is committed
Every aerolog-scaling milestone since 11ai spent 1.5 to 2.5 hours recomputing the same 48-layout inputs. A 466 KB exact JSON file now replaces that.
-
Census jobs data tells you which drone operators will conflict. It doesn't yet tell you how to split them
Weighting drone customers by census jobs makes paper conflict weights match the simulator (r 0.99, was 0.96); jobs plus residents match the split's median.
-
Does knowing where the water is help you plan drone altitude layers? A little
Spreading drone customers over New York's land, not the whole disc, puts a paper layer plan within 5% of the closed form in 17 of 24 layouts, up from 13.
-
Drone delivery with several operators: hubs never collide, operators do, and the semicircular rule helps
One operator's hubs never interfere. With four overlapping operators, a third of conflicts are crossings; the semicircular rule leaves 3x fewer.
-
Extra drone altitude layers: separate the overlapping operators, not the speeds
With four delivery operators, layering apart the most-overlapping ones cut en-route conflicts 2.3x to 3.7x against an in/out split. Speed bands did worse.
-
Hub distance is not enough to assign drone operators to altitude layers
On 24 random eight-operator layouts, assigning drone layers by hub distance left a median 14% more en-route conflicts than the closed form, up to 75% more.
-
Choosing drone altitude layers on paper: a one-page formula gets most of the way
A kinetic-gas formula on uniform service discs picks drone layers a median 2.6% off the closed form, against 13.6% for hub distance, with no traffic data.
-
Eight drone operators, four altitude layers: who should share?
Max-cut on closed-form conflict weights found the best two-group operator split every time. Market share over hub distance came within 2.2%.
-
Mixed-speed drone fleets: the semicircular rule still wins, but overtaking costs it most
With four delivery operators at 12 to 28 m/s, the semicircular altitude rule still leaves 57% fewer conflicts than an outbound/inbound split, down from 68%.
-
Sizing a cargo-drone hub's spare batteries with a formula instead of a simulator
For a battery-swap drone hub with 8 chargers, a short queueing recursion gives the same spare-pack count as the simulator: 12 to 45 packs.
-
How many spare batteries does a cargo-drone hub need when demand follows the clock?
A simulated 8-pad, 8-charger cargo-drone hub needs the same spare packs at 70% load but twice as many at 85% when demand follows a real daily profile.
-
Does charging a cargo-drone pack to 100% cost a hub more than charging to 90%?
A CC-CV curve fitted to a Molicel P45B datasheet shows a 20-90% charge costs 3% more than linear, but charging the same energy to 100% takes 1.7x as long.
-
How many spare batteries does a cargo-drone hub need when orders arrive in bursts?
A queueing simulation of a cargo-VTOL hub: batches of eight orders need about four times the spare packs that Poisson arrivals do.
-
How much grid power does a cargo-drone hub need?
A sized 100 kg-payload battery VTOL carries about 12 kWh; eight chargers at 1C draw 0.09 MW.
-
Which battery cell decides when a hybrid cargo drone beats a battery one?
In our cargo VTOL sizing model, four published Molicel 21700 cells move the hybrid-versus-battery break-even range from 44 km down to 22 km.
-
What first-order sensitivity hid in a hybrid-VTOL sizing model
Total-effect Sobol indices show three inputs a first-order ranking calls irrelevant carry about a tenth of the variance each.
-
Which input decides when a hybrid cargo VTOL beats a battery one?
A global sensitivity run on a cargo VTOL sizing model: the battery's peak power, not its energy density, decides the break-even range.
-
NeuralFoil's lift slope is 20 to 30% too steep on a third wing section
Against measured NACA 64A010 data, NeuralFoil's lift slope is 1.23 to 1.27 times measured at Reynolds 1e5 to 2e5, as on three other sections.
-
A sub-scale tail redesign survives a 25% lift-slope error
Cutting the tail lift slope by up to 25%, NeuralFoil's measured error, leaves the same 6 of 17 wings with a tail that restores the full-size flight modes.
-
Seven NASA air-taxi designs say a cargo VTOL's airframe weighs 48 to 62% of takeoff weight, not 40%
A hover-plus-L/D model reproduces NASA fuel weights for two turboshaft air taxis; their non-energy weight fraction is 0.48 to 0.62, not our 0.40.
-
Why our cargo-drone range model was 1.8x optimistic on a real aircraft
A mass-fraction range model gave 167 km for a 25 kg cargo VTOL that publishes 94 km. The gap is cruise drag, plausibly four stopped rotors.
-
A wing lift-slope error changes which scaled wing a tail can match
Cutting the wing's lift slope by 20% in a sub-scale UAV tail search shrinks the matching wings from 6 to 5 and swaps them for different wing-loading factors.
-
How many idle rotors explain a delivery drone's range claim?
Four stopped lift rotors of the Wingcopter 198 would add enough drag to match its quoted 94 km range; all eight would overshoot it. A plausibility range.
-
Fixing one sourced number shrinks the Wingcopter drag gap
Fixing the Wingcopter 198 wingspan at its published 1.98 m shrinks the zero-lift drag needed to match its quoted 94 km range to 1.5 to 3 times a clean airframe.
-
Does a 19% angle-of-attack gain error break fitting a UAV's flight modes?
A simulated fit of a small UAV's flight modes survives a CFD-derived alpha-probe error (gain 1.19, offset 0.6 deg) if the fit has a bias term.
-
A fitted sensor bias rescues a flight-dynamics fit up to 1 degree, not 2
A fitted per-channel bias repairs an output-error mode fit under an alpha offset up to 1 degree; at 2 degrees many 2-period fits fail.
-
Does airframe upwash push an angle-of-attack probe past our flight-fit limit?
CFD of a small blended-wing-body UAS gives a 0.6 degree upwash offset and a 19% slope error on angle of attack; our simulated fit tolerates 1.25 degrees.
-
How big a wind-vane error can a fitted bias absorb? A cliff at 1.25 to 1.5 degrees
In a Froude-scaled aircraft model, fitting one bias per sensor channel survives a 1.25 degree angle-of-attack error and fails abruptly by 1.5.
-
How much angle-of-attack bias can UAV system identification take?
A fitted bias repairs a constant angle-of-attack error up to 1 degree in a gust-response fit for a cargo aircraft model, and breaks between 1 and 2 degrees.
-
Would a real uncalibrated angle-of-attack probe break our flight-test fit?
A simulated output-error fit tolerates about 1.25 degrees of angle-of-attack bias. A published small-UAV five-hole probe calibration found 2.49 degrees.
-
A 1% pitot scale error costs the phugoid fit 2%, and one fitted bias removes it
Fitting flight modes from a scaled cargo-UAV model's airspeed channel: 0.25% scale error is harmless, 1% is not, and fitting a bias fixes it.
-
Does a pitot-tube error break a model aircraft's system-identification fit?
A 1% pitot offset can exceed the whole airspeed perturbation and break an output-error fit in every draw; one fitted bias per channel repairs it.
-
A propeller's thrust-speed slope: -2.25, and no sign it changes with Reynolds number
From 137 measured APC propeller curves, thrust at fixed RPM falls with speed as V^-2.25 near cruise, with no detectable Reynolds-number dependence.
-
When is constant power a fair thrust law for a cargo drone?
On 104 measured propeller curves the constant-power thrust slope of -1 holds within about 10% of the peak-efficiency advance ratio, and is -1.54 at 20% above.
-
A fitted slope repairs ramp drift in a scaled-drone model fit, but not a random walk on a long record
aerolog-scaling 9y: random-walk sensor drift hurts the output-error fit more than a ramp, and a fitted slope repairs it only on the short record.
-
A Froude-scaled model in rough air feels the right load and pitches too much
In Dryden turbulence a 1:5 Froude model of a cargo UAV keeps rms load factor within 2% but pitches 25 to 40% harder than the full-size aircraft.
-
Fit the IMU offset, or pay for it in a sub-scale flight test
A constant sensor offset of 10% of signal triples the error of an output-error fit of a model aircraft's modes. Four extra offset parameters remove it.
-
How loud is 10% sensor noise, for a real IMU?
Our scale-model identification tests add noise equal to 10% of each signal. A Bosch BMI088 datasheet says what that means in degrees per second.
-
When fitting a sensor offset makes the answer worse
A simulated test of drift in a sub-scale aircraft's sensors: a fitted constant offset can be worse than none, a fitted slope fixes it.
-
What a cheap IMU's zero offset does to a sub-scale flight test
A commodity MEMS IMU's data-sheet offset is larger than the whole signal in a gentle pitch doublet. After zeroing, temperature drift sets the floor.
-
Whitening for AR(1) noise recovers only half the loss when the real noise is AR(2) or 1/f
aerolog-scaling milestones 9p and 9q: an AR(1) iterated-GLS fit recovers half of the gust-prediction loss when sensor noise is AR(2) or 1/f, not four fifths.
-
Correlated sensor noise quietly skews a flight-test fit, and a cheap fix
Simulated flight-test fits with AR(1) sensor noise converge to slightly wrong modes; an iterated GLS fit recovers most of the loss.
-
A delivery drone spends 77% of its energy not cruising
On 134 measured Matrice 100 package-delivery flights, 77% of battery energy goes to climb, hover and acceleration, and one pack buys about 1 to 3 km one way.
-
A sub-scale cargo drone needs a tail you can adjust in flight
In simulation no fixed tail keeps a 1:5 cargo-UAV model's gust response within 10% if tail lift slope is 25% off; a tail area set in flight does, for 67 of 78.
-
Correlated sensor noise cost a model-identification fit 17 points of gust-prediction reliability, with no failures
aerolog-scaling milestone 9m: AR(1) noise at the same rms doubles short-period error in an output-error fit, silently, with zero fit failures.
-
Estimating the noise correlation costs nothing: milestone 9o of the scale-model study
Estimating the AR(1) noise correlation from residuals recovered the same gust-prediction reliability in a simulated scale-model aircraft fit as being told it.
-
Fitting a long, noisy flight record: start with one period
Starting an output-error fit from a one-period fit cut failures from 144 to 9 of 1,560 on noisy 4-period flight records.
-
How much energy does a delivery drone spend just climbing? Measured on 132 flights
In 132 measured Matrice 100 delivery flights, 25 m of altitude cost 9.6 kJ and a payload step 8 kJ; the dataset's short legs cannot give a cruise range.
-
What 134 measured drone flights say about delivering a package by air
Measured quadcopter flights give 63 J/m in cruise, but 77% of a flight's energy is climb and hover, and one battery buys 1 to 3 km.
-
Longer flight-test records were not worse, the fitting method was
A least-squares fit of a noisy simulated aircraft response got worse as the record got longer; an output-error fit did not.