In reference to application US20160239804:
I am wondering what is the legal situation here, "Thererefore, at least the following is claimed: *assessing weather along a route... *evaluating approach to drop *calculating amount of time "
This, and other subclaims are replicating capability of a product sold in small quantities circa 2009-2013 worldwide (Norway, Poland US, France, Czech Rep. to name a few) being integrated with unamanned aerial vehicles (UAVs: EasyUAV, Pteryx UAV, Demon UAV, and Manta/EasyMap UAV).
A computer performing said flight planning was FLEXIPILOT and in its flexipilot1.35-navigation-en manual that circulated on the web for years before the product was discontinued, one can achieve exactly this delivery functionality using UAV. It was designed for such missions, including Australian Outback Delivery Challenge, which was performed by similar control devices.
In case of FLEXIPILOT, weather was estimated prior to takeoff by entering variables SIM_WIN_SPEED and SIM_WIND_HEADING on its delivery console (which allowed communication via modem). For example command WPTITERALL was assessing total flight time both including or neglecting wind estimates, RETHOME logic is evaluating possible outcomes in realtime based on both its own internal estimate of wind speed and SIM_WIND_SPEED that could be transmitted and received at any moment, using those factors and published (exported to US for University) telemetry protocol FLEXIPILOT integrated with PTERYX device ws able to report in realtime flight times to takeoff, any of its emergency landign sites, projected time to impact earth at any time, and time to WPT_TARGET which was location of generalized geographic hook, relative to which any waypoint could be placed. Because relative placement of waypoints included the option of displacement and heading depending on wind direction estimate, device was effectively used for planning landing as a function of meteo conditions.
Because at any waypoint which could be looped one could perform any servo movement action using TRIGGER or PARA logic, this UAV control computer was capable and was tested for delivery missions and indeed similar missions were performed as early as 2010 by several contestans of DIYDRONES T2 contest - airdrop challenge (egg delivery) using also open-source counterparts of said autopilot. IMO there is nothing innovative in this patent, not even the fact that they are delivering a container which was subject of contests 6 years ago.
NOTE: I have also found this presentation on public diydrones forum, claiming almost identical behaviour for delivery drones: Pigeon Post presentation dated 2013-02-13 www.youtube.com/watch?v=3boZtKRseSA
FLEXIPILOT navigation manual is here, all versions are from 2013: https://drive.google.com/open?id=0B9-O1_5eWoN9Q2tNWUpvbndaV2s
FLEXIPILOT telemetry manual is here, showing sample display application for parameters https://drive.google.com/open?id=0B9-O1_5eWoN9WGZEenVINWtxaHc
FLEXIPILOT open source telemetry code: https://drive.google.com/open?id=0B9-O1_5eWoN9SGhib2xtMVhsNms which contains ID=12 time2ground variable with impact_type=2 designating payload delivery time