System and method of real time detection of aerial vehicle flight patterns and insurance policy updates

BACKGROUND

0001Technical Field

0002The present disclosure pertains to risk management for airborne vehicles and, more particularly, to providing real-time insurance adjustments for airborne vehicles based on current flight patterns and operator profile.

0003Description of the Related Art

0004Recent advancements in drone and unmanned aerial vehicle technology have greatly reduced the cost of these vehicles and made them readily available to the general public. Although these vehicles are more affordable than in previous years, replacement and repair costs are still relatively high for most users. Similarly, the cost of personal injuries and property damage caused by reckless or uncontrolled aerial vehicle operations may increase as more aerial vehicles are flown in suburban locations. It is with respect to these and other considerations that implementations of the present disclosure are provided.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

0005The foregoing and other features and advantages of the present disclosure will be more readily appreciated as the same become better understood from the following detailed description when taken in conjunction with the accompanying drawings, wherein:

0006<figref idref="DRAWINGS">FIG. 1</figref> is a context diagram that illustrates an example implementation of an environment that provides real-time insurance policy updates as described herein;

0007<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram that illustrates one implementation of a system for providing real-time insurance policy updates as described herein;

0008<figref idref="DRAWINGS">FIG. 3</figref> is a logical flow diagram that illustrates one implementation of a process for providing real-time insurance policy updates for an aerial vehicle and operator in response to current flight characteristics of the aerial vehicle; and

0009<figref idref="DRAWINGS">FIG. 4</figref> is a system diagram of computing systems for implementation of the process and method of the present disclosure.

DETAILED DESCRIPTION

0010In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed implementations. However, one skilled in the relevant art will recognize that the present disclosed implementations may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures or components or both that are associated with the environment of the present disclosure have not been shown or described in order to avoid unnecessarily obscuring descriptions of the implementations.

0011Throughout the specification, claims, and drawings, the following terms take the meaning explicitly associated herein, unless the context clearly dictates otherwise. The term “herein” refers to the specification, claims, and drawings associated with the current application.

0012Unless the context requires otherwise, throughout the specification and claims that follow, the word “comprise” and variations thereof, such as “comprises” and “comprising” are to be construed in an open inclusive sense, that is, as “including, but not limited to.” The foregoing applies equally to the words “including” and “having.”

0013The phrases “in one implementation,” “in another implementation,” “in various implementations,” “in some implementations,” “in other implementations,” and other variations thereof refer to one or more features, structures, functions, limitations, or characteristics of the present disclosure, and are not limited to the same or different implementations unless the context clearly dictates otherwise.

0014As used herein, the term “or” is an inclusive “or” operator, and is equivalent to the phrases “A or B, or both” or “A or B or C, or any combination thereof,” and lists with additional elements are similarly treated. The term “based on” is not exclusive and allows for being based on additional features, functions, aspects, or limitations not described, unless the context clearly dictates otherwise. In addition, throughout the disclosure, the meaning of “a,” “an,” and “the” include singular and plural references.

0015The following are various definitions of terms utilized herein to provide a general description of the terms, but are not intended to be an exclusive or exhaustive description.

0016As used herein, the terms “aerial vehicle” and “vehicle” may be used interchangeably and refer to a powered airborne object controlled by an operator or controlled autonomously. Examples of aerial vehicles include, but are not limited to, unmanned aerial vehicles, drones, manned aerial vehicles, fixed-wing aircraft, rotor-wing aircraft, vertical takeoff and landing systems, or the like, or some combination thereof. Aerial vehicles are also referred to as airborne vehicles.

0017As used herein, the term “remote control” refers to a device that is used to manually operate an aerial vehicle from a location remote to the aerial vehicle.

0018As used herein, the terms “Applicant,” “Insured,” and “Operator” may be used interchangeably and refer to a human, group of people, company, organization, or legal entity that applies for insurance, who has insurable interest in the aerial vehicle to be insured, and who provides the operational parameters, either manually or remotely, that result in the control of the operation of an aerial vehicle.

0019As used herein, the term “monitoring system” refers to a system that collects information regarding the operation of an aerial vehicle, including aerial-vehicle operational data and remote-control operational data. The monitoring system includes a vehicle monitoring system and a remote monitoring system. The vehicle monitoring system and a remote monitoring system include a plurality of different sensors to collect the operational data associated with the aerial vehicle and the operator. If installation of sensors is required by the operator, the operator initiates or performs a “system check” function prior to the monitoring system being operationally activated to make sure the monitoring system is properly calibrated prior to operation of the aerial vehicle. In some instances, the aerial vehicle may be non-operational until the monitoring system is installed, calibrated, and dynamic insurance is enabled.

0020The vehicle monitoring system includes onboard sensors, remote sensors, or a combination thereof to collect current flight characteristics and aerial-vehicle operational data of the aerial vehicle. The vehicle monitoring system may be on the aerial vehicle or data about the aerial vehicle may be collected remotely. The vehicle monitoring system may include, but is not limited to, an inertial measurement unit (IMU), gyroscope, magnetometer, accelerometer, altimeter or altitude meter, airspeed sensor or speedometer, engine or motor Revolutions Per Minute (RPM) monitor, course heading, Vertical Speed Indicator (VSI), Global Positioning System (GPS) (location of the vehicle, the operator, and the relation of one to the other), G-force sensor, acceleration and deceleration sensors, and other sensors to measure the roll, yaw, and pitch or their rates of change. The vehicle monitoring system is used to record whether the vehicle is in an on state or an off state, the duration of operation, location relative to fixed or known geographic markers, if it is moving, how it is moving, patterns of flight, pitch, roll, yaw, vertical and horizontal acceleration, speed, and altitude, as well as abrupt movements caused by contact with an object that is fixed or moving.

0021The remote monitoring system includes various sensors to collect characteristics and remote-control operational data of the operator as they operate the aerial vehicle. These characteristics provide information as to the operator's control of the aerial vehicle and how the operator responds to various conditions of the aerial vehicle. For example, does the operator react quickly or sporadically to control the vehicle in response to the vehicle's location, movement, or operation, or does the operator provide a more fluid and calculated control of the vehicle regardless of its location, movement, or operation. In some implementations, this remote monitoring system may be integrated into or separate from the actual remote control used by the operator to control the aerial vehicle. In at least one implementation, the remote monitoring system may also include one or more biological sensors (e.g., fingerprint, retina, or cardio-rhythmic sensors) that can be used to identify the operator of the aerial vehicle. In this way, the system knows if the current operator hands the remote control to a different operator, which can be used to further adjust the insurance coverage during operation of the aerial vehicle.

0022As used herein, the term “operational data” refers to data, both real-time and historical, that is collected by a monitoring system of an aerial vehicle to identify behavioral data or flight characteristics of the operator and aerial vehicle as the operator operates the aerial vehicle. Operational data includes aerial-vehicle operational data collected from the aerial-vehicle monitoring system and remote-control operational data collected from the remote-control monitoring system.

0023Aerial-vehicle operational data includes various flight characteristics associated with the movement or operation of the aerial vehicle, such as, but not limited to, altitude, airspeed, vertical and horizontal velocity and acceleration, engine or motor revolutions per minute (RPM), course heading, location of the aerial vehicle, G-force information, on/off state information, duration of operation, vehicle orientation, and rate of roll, yaw, and pitch. This aerial-vehicle operational data is utilized to determine a current flight pattern of the aerial vehicle.

0024Remote-control operational data includes various flight characteristics associated with how the operator controls the aerial vehicle and responds to the movement of the aerial vehicle, such as, but not limited to, type, rate, and reaction time of operator response to aerial vehicle movement, location, or operation. This remote-control operational data is utilized, along with the aerial vehicle operational data, to determine an operator profile for the operator.

0025Operational data also includes weather and other environmental characteristics, both real-time and historical, associated with the operation of an aerial vehicle. For example, the operational data of historical flights that resulted in an incident includes the weather at time of the incident and at the location of the incident, e.g., the temperature, cloud covering, precipitation, time of day, or other environmental characteristics at the time and location of the incident or the seconds or minutes leading up to the incident. Similarly, the operational data of a current flight includes the current weather at the location of the aerial vehicle, e.g., current temperature, current precipitation, current cloud cover, current time of day, or other environment characteristics in real time as the aerial vehicle is being operated.

0026As used herein, the terms “behavioral data” and “flight characteristics” may be used interchangeably and refer to the nature of how an operator and aerial vehicle interact with or without a remote control. Behavioral data is comprised of a plurality of different operational data, where each separate operation datum is a separate flight characteristic. For example, airspeed and altitude are aerial-vehicle operational data, where airspeed is one flight characteristics and altitude is a separate flight characteristic. The behavioral data is utilized to create an operational history of the aerial vehicle and to generate an operator profile for the current operator of the aerial vehicle.

0027As used herein, the term “operational history” refers to the current or previous operation of one or more aerial vehicles based on behavioral data generated and collected in real time and over time. Operational history may be generated for an individual operator or for an individual aerial vehicle, such as a target aerial vehicle for which a particular operator is purchasing insurance. Operational history may also be generated from the aggregation of behavioral data from a plurality of operators or a plurality of aerial vehicles. The operational history includes current flight patterns of the aerial vehicle, as well as historical flight patterns (e.g., flight patterns that resulted in incidents) or other information associated with one or more aerial vehicles.

0028The operational history is used to generate and change a risk profile of an operator and to adjust insurance rates or coverage of relative operations of an aerial vehicle. Operational history can provide insight into certain fight patterns or operations that result in higher incident occurrences, such that when those patterns are flown in the future by an operator, higher rates can be applied to that operator. For example, specific previous flight patterns and factors will reveal higher levels of incident occurrence that will result in increased rates while a current flight pattern matching the previous flight patterns is being flown.

0029As used herein, the term “incident” refers to an event or accident that resulted in damage to a person or property, ticket, citation, confiscation of the aerial vehicle, or other action cause by unsafe or unlawful use of the aerial vehicle.

0030As used herein, the term “flight pattern” refers to a plurality of flight characteristics at a given point in time or collected over a time period of operation. One non-exhaustive example flight pattern may be the current airspeed and current altitude of an aerial vehicle. Another non-exhaustive example flight pattern may be the airspeed and altitude at time T<b>1</b>, the rate or roll at time T<b>2</b>, and the RPMs at time T<b>3</b>. A current flight pattern of an aerial vehicle is a flight pattern that is occurring in real time during operation of the aerial vehicle. A previous flight pattern of an aerial vehicle is a flight pattern that occurred during prior operation of the aerial vehicle. Previous flight patterns that resulted in incidences along with other data are used to define unsafe flying, and previous flight patterns that resulted in no incidences are used to define safe flying.

0031As used herein, the term “operator profile” refers to information associated with how a current operator of an aerial vehicle is operating that particular aerial vehicle. The operator profile is generated from the behavioral data associated with the operator and aerial vehicle. The operator profile is modified in real time as the operator operates the aerial vehicle.

0032As used herein, the term “risk profile” refers to information associated with how an aerial vehicle is operating relative to historical information of one or more other aerial vehicles. The risk profile identifies a level of potential incident or insurance claim—based on how the aerial vehicle is operating and who is operating the aerial vehicle—which the insurance company may have to pay on behalf of the insured if an incident were to occur. The risk profile is dynamically generated or adjusted based on an analysis of the operational history and the operator profile. Other information (e.g., risk information, aerial vehicle information, and operator information) is also used to generate and adjust the risk profile.

0033The risk profile is used to determine the rates and coverage for an aerial vehicle and operator as the operator is operating the aerial vehicle. A higher risk profile is an indication of a greater chance of a claim, which results in higher rates and lower available coverage. A lower the risk profile is an indication of a lower chance of a claim, which results in lower relative rates and higher available coverage. The risk profile can change over time as the aerial vehicle is being operated. So, if the operator begins to fly the aerial vehicle in an identified and predetermined safe manner, then the risk profile may decrease. But if the operator begins to fly the aerial vehicle in an identified and predetermined unsafe manner, then the risk profile may increase.

0034Some experienced operators will be able to operate smaller aerial vehicles in congested areas during poor weather conditions and operate with a consistent pitch, roll, yaw, attitude, speed, and altitude while keeping distance from fixed objects—demonstrating a lower risk profile, resulting in favorable insurance rates from the insurance company. Alternatively, a low experience operator will have difficulty maintaining a consistent altitude, frequent change in pitch/roll and acceleration while operating a large vehicle in low density open areas with clear line of sight—demonstrating a higher risk profile, resulting in less favorable insurance rates from the insurance company.

0035The amount at which the risk profile changes is based on the experience level of the operator, how the operator is operating the aerial vehicle, and the current flight characteristics of the aerial vehicle. So, a more experienced operator operating the aerial vehicle in a particular manner may result in a smaller increase or larger decrease in the risk profile compared to a less experience operator operating the aerial vehicle in the same particular manner. Over time, as interactions of the operator and aerial vehicle are recorded, the operator will likely demonstrate improved proficiency in the operation of the aerial vehicle resulting in a lowered risk profile from the insurance company.

0036As used herein, the term “insurance” refers to a product used to transfer a portion or all of the risk of property damage or liability from one party to another, such as an insurance company, resulting in the payment of a premium in exchange for the insurance.

0037As used herein, the term “rates” refers to pricing that reflects a premium the insurance company is willing to receive in exchange for the transfer for the desired level of risk, either property or liability, to the insurance company.

0038As used herein, the terms “billing” or “invoicing” refer to an initial premium agreed upon at the inception of the policy, and an additional or return premium due to changes in rates or coverage as the risk profile is modified as an operator operates the aerial vehicle over the policy period.

0039As used herein, the term “policy issuance” refers to applicant and vehicle information that is provided and transferred to the fillable fields of the insurance policy and delivered to the Insured and provides an acknowledgement of receipt.

0040As used herein, the term “user interface” refers to a system accessed through a computer or mobile device that is used to gather and deliver information to or from the operator, including but not limited to the initial application for insurance, a coverage request (binding), the issued insurance policy, billing information, invoicing, vehicle operational data (real-time and historical), operator profile, aerial vehicle registration information, and additional coverage or certificates of insurance. In some implementations the user interface may be through a web browser accessible via an operator's smartphone, desktop computer, laptop, tablet, or other operator computing device.

0041As used herein, the terms “risk generator” and “risk generator computing device” refer to a computer, server, or other computing system that dynamically and automatically adjusts an insurance policy for an aerial vehicle operator in real-time as the operator is operating the aerial vehicle. The risk generator computing device receives applicant/operator information, aerial-vehicle information, aerial-vehicle operational data, remote-control operational data, operational historical data of other aerial vehicles, risk information, or other operator, aerial vehicle, or insurance information. The risk generator aggregates and analyzes the received data to determine and adjust a risk profile for the operator and aerial vehicle. The risk profile is used to generate and dynamically modify an insurance policy for the operator. The risk generator also generates the appropriate billing documentation based on the ever-changing insurance policy. The risk generator, which is further described in conjunction with <figref idref="DRAWINGS">FIG. 4</figref>, includes, among other physical computing components, a memory that stores instructions and a processor that executes the instructions to perform various actions described herein.

0042As used herein, the term “satellite” refers to a system used to transmit data and provide GPS location information.

0043Described herein are systems and methods to provide a real-time insurance solution for aerial vehicles operated remotely or manually using historical operations data, real-time operational data, or a combination thereof. The operational data is based on the behavior of the operator or the vehicle, or both, which are collected using monitoring systems, sensors, and software.

0044<figref idref="DRAWINGS">FIG. 1</figref> is a context diagram that illustrates an example implementation of an environment <b>100</b> that provides real-time insurance policy updates. The environment <b>100</b> includes an aerial vehicle <b>102</b> and a risk generator computing device <b>114</b>, among other components described herein.

0045The operation and movement of the aerial vehicle <b>102</b> is controlled by an operator <b>106</b> via a remote control <b>104</b>. Although in some implementations, the aerial vehicle <b>102</b> may be operated autonomously without the remote control <b>104</b>. As described herein, the aerial vehicle <b>102</b> includes an aerial-vehicle monitoring system <b>122</b> that monitors the movement and flight characteristics of the aerial vehicle <b>102</b> to obtain aerial-vehicle operational data. Although <figref idref="DRAWINGS">FIG. 1</figref> shows the vehicle monitoring system <b>122</b> as being part of the aerial vehicle <b>102</b>, implementations are not so limited and the vehicle monitoring system <b>122</b> may be integrated into the aerial vehicle <b>102</b>, separate from but attached to the aerial vehicle <b>102</b>, or remotely located from the aerial vehicle <b>102</b>.

0046The aerial-vehicle operational data collected from the vehicle monitoring system <b>122</b> is provided to the risk generator computing device <b>114</b> via a communication network <b>110</b>. Some aerial vehicles <b>102</b> may not have the electrical power or electrical components to communicate with the communication network <b>110</b>. In at least one such implementation, the aerial vehicle <b>102</b> may provide the collected aerial-vehicle operational data to the remote control <b>104</b> or some other computing device (not illustrated), which forwards the data to the risk generator computing device <b>114</b> via the communication network <b>110</b>.

0047In some implementations, the remote control <b>104</b> includes a remote-control monitoring system <b>124</b> to obtain remote-control operational data by monitoring responses and actions performed by the operator <b>106</b> while operating the aerial vehicle <b>102</b>. Although <figref idref="DRAWINGS">FIG. 1</figref> shows the remote monitoring system <b>124</b> as being part of the remote control <b>104</b>, implementations are not so limited and the remote monitoring system <b>124</b> may be integrated into the remote control <b>104</b>, separate from but attached to the remote control <b>104</b>, or remotely located from the remote control <b>104</b>.

0048The remote control <b>104</b> may provide the collected operational data to the risk generator computing device <b>114</b> via the communication network <b>110</b>. Alternatively, the remote control <b>104</b> may provide the collected remote-control operational data to the aerial vehicle <b>102</b> or some other computing device (not illustrated), which forwards the data to the risk generator computing device <b>114</b> via the communication network <b>110</b>.

0049The collected operational data is provided to the risk generator computing device <b>114</b> in real time or near real time as the data is collected during the operation of the aerial vehicle <b>102</b>. In this way, the risk generator computing device <b>114</b> can constantly change, modify, or otherwise update the insurance rates or coverage for the operator <b>106</b> and the aerial vehicle <b>102</b> in real time as the operator <b>106</b> operates the aerial vehicle <b>102</b>.

0050The communication network <b>110</b> includes one or more wired or wireless communication mechanisms, such as, the Internet, Bluetooth®, Wi-Fi, satellite link, or other known communication methods that can transmit data from the aerial vehicle <b>102</b> or the remote control <b>104</b> to a remote computing device (e.g., the risk generator computing device <b>114</b>).

0051As described herein, the risk generator computing device <b>114</b> aggregates and analyses the operational data received from the aerial vehicle <b>102</b> or the remote control <b>104</b> to dynamically generate and adjust insurance rates and coverage for the operator <b>106</b> and the aerial vehicle <b>102</b>. In some implementations, the risk generator computing device <b>114</b> receives insurance information from an insurance company <b>118</b>. This information may include, different available rates or coverages, information about the operator <b>106</b> (e.g., personal information, history of previous incidents, experience level, training certifications, or other operator information related to how that operator may operate the aerial vehicle <b>102</b>), information about the aerial vehicle <b>102</b> (e.g., history of previous incidents for that particular aerial vehicle, as well as other aerial vehicles of the same make and model, previous flight patterns associated with incidents, or other historical operational data related to the operation of the aerial vehicle <b>102</b>), or other risk-related information associated with the aerial vehicle <b>102</b> or the operator <b>106</b>.

0052The risk generator computing device <b>114</b> may provide the resulting rates and coverage to the insurance company <b>118</b> or it may provide it to the operator <b>106</b> via an operator computing device <b>108</b>. The operator computing device <b>108</b> may be a mobile phone, tablet computer, smartphone, desktop computer, laptop computer, or other commuting device.

0053The operator <b>106</b> may utilize a user interface of the operator computing device <b>108</b> to access an application, website, or other informational portal of the risk generator computing device <b>114</b> or the insurance company <b>118</b> to receive or obtain access to the rates, coverages, or other insurance information associated with the insurance provided by the insurance company <b>118</b> as determined and dynamically adjusted by the risk generator computing device <b>114</b>. The operator <b>106</b> may also utilize the user interface of the operator computing device <b>108</b> to select, change, or access coverage, policy issuance, billing, or invoicing information.

0054<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram that illustrates one implementation of a system <b>200</b> for providing real-time insurance policy updates. The system <b>200</b> includes an aerial vehicle <b>102</b> and a risk generator computing device <b>114</b>. As described above in conjunction with <figref idref="DRAWINGS">FIG. 1</figref>, the operation and movement of the aerial vehicle <b>102</b> is controlled by an operator <b>106</b> via a remote control <b>104</b>.

0055The system <b>200</b> also includes an aerial-vehicle monitoring system <b>122</b> and a remote-control monitoring system <b>124</b>. The aerial-vehicle monitoring system <b>122</b> includes a plurality of sensors to monitor the operating and flight characteristics of the aerial vehicle <b>102</b>. The vehicle monitoring system <b>122</b> provides the monitored and collected information to the risk generator computing device <b>114</b> as aerial vehicle operational data <b>206</b>. The remote-control monitoring system <b>124</b> includes a plurality of sensors to monitor the remote control <b>104</b> inputs and reactions of the operator <b>106</b> as the operator <b>106</b> is operating the aerial vehicle <b>102</b>. The remote monitoring system <b>124</b> provides the monitored and collected information to the risk generator computing device <b>114</b> as remote-control operational data <b>208</b>.

0056The risk generator computing device <b>114</b> aggregates the aerial-vehicle operational data <b>206</b> and the remote-control operational data <b>208</b> into behavioral data <b>210</b>. The behavioral data <b>210</b> is utilized to generate an operational history <b>224</b> of the aerial vehicle <b>102</b>. The operational history <b>224</b> includes a consistently updating current flight pattern of the aerial vehicle <b>102</b>, as well has previous flight patterns of the aerial vehicle <b>102</b> or other aerial vehicles (not illustrated). The risk generator computing device <b>114</b> generates the current flight pattern of the aerial vehicle <b>102</b> based on a combination of a plurality of behavioral data <b>210</b>. Similarly, the risk generator computing device <b>114</b> generates one or more previous flight patterns from historical data <b>222</b>. The historical data <b>222</b> may include behavioral data of aerial vehicles that were previously involved in an incident or previous flight patterns that resulted in an incident.

0057The behavioral data <b>210</b> is also utilized to generate an operator profile <b>226</b> of the operator <b>106</b>. The operator profile <b>226</b> indicates how well the operator <b>106</b> is operating the aerial vehicle <b>102</b>. In some implementations, the operator profile <b>226</b> includes a score regarding how experienced or risky the operator <b>106</b> is being in operating the aerial vehicle <b>102</b>.

0058The operator profile <b>226</b> is based on the actions the operator <b>106</b> took to correct, change, or maneuver the operating parameters (e.g., flight path or orientation) of the aerial vehicle <b>102</b>, as well as how fluid are those actions. The actions the operator <b>106</b> takes include what controls the operator <b>106</b> activated on the remote control <b>104</b>, reaction time (e.g., how long it took the operator <b>106</b> to take the action), did the operator <b>106</b> over-correct the aerial vehicle <b>102</b>, or other behaviors that the operator <b>106</b> takes to operate the aerial vehicle <b>102</b>. For example, if the aerial vehicle <b>102</b> instantly pitches upward due to a wind gust, how long does it take for the operator <b>106</b> to correct the pitch, what controls on the remote control <b>104</b> does the operator <b>106</b> activate to correct the pitch, and how fluid were those controls. This information is compared to one or more thresholds, ranges, or proficiently levels, and then combined to create the operator profile <b>226</b>.

0059The risk generator computing device <b>114</b> utilizes the operational history <b>224</b> to generate a risk profile <b>212</b>. The risk profile <b>212</b> provides an indication of whether the current flight pattern is the same or within some threshold as a previous flight pattern that resulted in an incident. In some implementations, the risk profile <b>212</b> includes a score of the likelihood the aerial vehicle <b>102</b> will also be in an incident based on a comparison of its current flight pattern to one or more previous flight patterns. The risk generator computing device <b>114</b> computes this risk profile <b>212</b> score by comparing the current flight pattern of the aerial vehicle <b>102</b> to the previous flight patterns in the operational history <b>224</b> to obtain the deviation between the current flight pattern and the previous flight patterns. A higher likelihood of an incident occurring (e.g., a higher risk profile score) may be based on the current flight pattern being more similar to a previous flight pattern that ended in an incident (e.g., lower deviation between current flight pattern and one or more previous flight patterns that resulted in an incident), whereas a lower likelihood of an incident occurring (e.g., a lower risk profile score) may be based on the current flight pattern being more different that the previous flight patterns (e.g., higher deviation between current flight pattern and previous flight patterns that resulted in an incident). The higher the risk profile, the more unsafe the aerial vehicle is operating, and the lower the risk profile, the safer the aerial vehicle is operating.

0060The risk generator computing device <b>114</b> adjusts the risk profile <b>212</b> based on the operator profile <b>226</b>. Since the operator profile <b>226</b> provides an indication of how the operator <b>106</b> is operating the aerial vehicle <b>102</b>, it can be used to increase or decrease the risk profile <b>212</b>. For example, if the aerial vehicle <b>102</b> is performing a maneuver that has a high likelihood of an incident (e.g., because numerous other aerial vehicles have been in incidents performing the same maneuver), then the risk profile may be determined to be very high. But the risk profile may be lowered if the operator profile indicates that the operator is experienced and accurately and efficiently operating the aerial vehicle as it performs the maneuver, or the risk profile may be increased if the operator profile indicates an inexperienced or risky operator profile.

0061In some implementations, the risk profile <b>212</b> is further generated or modified based on other information, such as vehicle information <b>216</b>, risk information <b>220</b>, or operator information <b>218</b>. For example, the vehicle information <b>216</b> may include a make, model, year, total number of operating hours, history of defects or malfunctions, manufacture recalls, history of incidents, or other information associated with the aerial vehicle <b>102</b>. The operator information <b>218</b> may include a total number of hours that the operator <b>106</b> has operated the aerial vehicle <b>102</b>, previous aerial vehicle incidents, total number of hours that the operator <b>106</b> has operated other aerial vehicles, previously demonstrated ability to operate the aerial vehicle <b>102</b>, certifications, registrations, or other information associated with the operator <b>106</b>. The risk information <b>220</b> may include one or more thresholds, ranges, proficiency levels, or other risk criteria that are used to compare against the operational history <b>224</b>, operator profile <b>226</b>, vehicle information <b>216</b>, and operator information <b>218</b> to generate and adjust the risk profile <b>212</b>.

0062The risk generator computing device <b>114</b> utilizes the risk profile to automatically generate and update rates and coverage <b>214</b> for an insurance policy for the aerial vehicle <b>102</b> and the operator <b>106</b> in real time as the operator <b>106</b> is operating the aerial vehicle <b>102</b>. So as the operator <b>106</b> is operating the aerial vehicle <b>102</b>, the vehicle monitoring system <b>122</b> and the remote monitoring system <b>124</b> collect aerial-vehicle operational data <b>206</b> and remote-control operational data <b>208</b>, respectively, and provide it to the risk generator <b>114</b>. The risk generator <b>114</b> collects this real-time behavioral data <b>210</b> and generates the operational history <b>224</b> and the operator profile <b>226</b>, which is used to dynamically adjust the risk profile <b>212</b> so that the rates and coverage <b>214</b> reflect real-time liability during operation of the aerial vehicle <b>102</b>.

0063<figref idref="DRAWINGS">FIG. 3</figref> is a logical flow diagram that illustrates one implementation of a process <b>300</b> for providing real-time insurance policy updates for an aerial vehicle and operator in response to current flight characteristics of the aerial vehicle. The process <b>300</b> begins at block <b>310</b>, where one or more previous flight patterns are generated for one or more aerial vehicles that were involved in an incident. Each previous flight pattern is generated in response to previous flight characteristics of a respective aerial vehicle prior to the respective incident. A previous flight pattern may be a combination of a plurality of flight characteristics at a given point in time at or prior to an incident, or a plurality of flight characteristics over a period of time prior to the incident.

0064The process <b>300</b> proceeds to block <b>312</b>, where current flight characteristics of a target aerial vehicle are obtained. The target aerial vehicle is the aerial vehicle being operated by a current operator who is purchasing a dynamic insurance policy for the aerial vehicle while it is being operated. The current flight characteristics are obtained via signals received from a plurality of sensors of a monitoring system associated with the target aerial vehicle. Each of the received signals indicates a unique current flight characteristic of the target aerial vehicle. For example, the current flight characteristics may include aerial-vehicle operational data or remote-control operational data, or a combination thereof, from an aerial-vehicle monitoring system or a remote-control monitoring system, respectively.

0065The process <b>300</b> continues at block <b>314</b>, where an operator profile is generated for the current operator of the target aerial vehicle. The operator profile is generated based on the current flight characteristics of the target aerial vehicle as the target aerial vehicle is being operated by the current operator. As described herein, the operator profile may be a score or other information that indicates how well the current operator is operating the target aerial vehicle.

0066The process <b>300</b> proceeds to block <b>316</b>, where a current flight pattern is generated for the target aerial vehicle. The current flight pattern is an ever changing combination of one or more of the plurality of obtained current flight characteristics. Similar to the previous flight pattern, the current flight pattern may be a plurality of current flight characteristics at a given point in time, or a plurality of current flight characteristics over a prior time period (generally ending at the present operating time), which is continuously changing as the aerial vehicle is being operated.

0067The process <b>300</b> continues at block <b>318</b>, where a current risk profile is generated based on a comparison of the current flight pattern and at least one of the one or more previous flight patterns. One or more different threshold values, ranges, performance levels, or other operational indicators may be used to determine how similar the current flight pattern is to at least one previous flight pattern. This comparison of flight patterns, when evaluated against the operational indicators, provides information (e.g., a value or score) indicative of a likelihood that the target aerial vehicle will be in an incident (e.g., an incident similar to the incident associated with the previous flight pattern).

0068At block <b>320</b> the current risk profile is adjusted based on the operator profile. Since the operator profile indicates how well the current operator is operating the aerial vehicle, it is used to increase or decrease the current risk profile. The risk profile is adjusted such that the better the operational profile of the operator the more favorable the insurance available, which may include lower rates, higher limits of coverage, and expanded provisions. For example, a higher operator profile (e.g., indicating that the current operator is experienced and can efficiently and effectively operate the target aerial vehicle) may result in a decrease in the risk profile. In contrast, a lower operator profile (e.g., indicating that the current operator is inexperienced and cannot efficiently and effectively operate the target aerial vehicle) may result in an increase in the risk profile. Again, various thresholds or ranges may be employed to determine an amount to increase or decrease the risk profile, or not adjust the risk profile, based on the operator profile.

0069Referring next to block <b>322</b>, an insurance policy for the target aerial vehicle (or the current operator) is automatically updated in response to changes in the current risk profile. As the current operator operates the target aerial vehicle and the current flight characteristics change, the operator profile and the current risk profile may change in response to the changed current flight characteristics, which results in an insurance policy that dynamically changes in real time as the current operator operates the target aerial vehicle.

0070After block <b>322</b>, the process loops back to block <b>310</b> to continue to obtain current flight characteristics of the target aerial vehicle, which are used to continually change the risk profile and the operator profile to provide dynamic, real-time changes to the insurance policy for the target aerial vehicle.

0071<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of system <b>400</b> of computing systems for implementation of the process and method of the present disclosure. The system <b>400</b> includes a risk generator computing device <b>114</b> and an operator computing device <b>108</b>, as described herein.

0072One or more general-purpose or special-purpose computing systems are used to implement the risk generator computing device <b>114</b>, to dynamically adjust an insurance policy for an aerial vehicle or operator in real time as the operator is operating the aerial vehicle as described herein. Accordingly, various implementations described herein may be implemented in software, hardware, firmware, or in some combination thereof.

0073The risk generator computing device <b>114</b> includes a memory <b>404</b>, one or more central processing units (CPUs) <b>416</b>, a display device <b>418</b>, other I/O device or interfaces <b>420</b>, other computer-readable media <b>422</b>, and network connections <b>424</b> (configured to communicate with other computing devices via a wired or wireless communication network, such as communication network <b>110</b>). The other I/O devices <b>420</b> can include a keyboard, audio interfaces, video interfaces, or the like.

0074The memory <b>404</b> utilizes one or more various types of non-volatile or volatile storage technologies. Examples of memory <b>404</b> include, but are not limited to, flash memory, hard disk drives, optical drives, solid-state drives, various types of random access memory (RAM), various types of read-only memory (ROM), other computer-readable storage media (also referred to as processor-readable storage media), or other memory technologies, or any combination thereof. The memory <b>404</b> may be utilized to store information, including computer-readable instructions that are utilized by the CPU <b>416</b> to perform actions, including aspects, implementations, and features described herein.

0075The memory <b>404</b> has stored thereon a behavioral data system <b>406</b> or a risk profile system <b>408</b>. The behavioral data system <b>406</b> performs various functions described herein to aggregate operational data received from the monitoring system(s) of an aerial vehicle. The risk profile system <b>408</b> performs various functions described herein to generate an operational history of the aerial vehicle and an operator profile for the operator that is operating the aerial vehicle. The risk profile system <b>408</b> utilizes the operational history and operator profile to generate and adjust—in real time as the operator is operating the aerial vehicle—a risk profile that is used to generate or update an insurance policy for the operator or aerial vehicle. The memory <b>404</b> may also store other programs <b>412</b>, operator and vehicle data <b>414</b> (to store vehicle information, operator information, behavioral data, operator profile data, or behavioral history data), or a rates and coverage database <b>415</b> (to store information regarding insurance policy rates and coverages available to operators).

0076The operator computing device <b>108</b> may be implemented by one or more general-purpose or special-purpose computing systems employing software, hardware, firmware, or some combination thereof. Accordingly, these devices and systems include a memory <b>452</b>, a CPU <b>466</b>, a display <b>468</b>, other computer readable media <b>472</b>, other I/O devices <b>470</b>, and network connections <b>474</b>, which may be similar to those same components described above for the risk generator computing device <b>114</b>. The memory <b>452</b> may store instructions for a various computer applications, such as a browser <b>454</b> or other programs <b>456</b>. The memory <b>452</b> may also store other data <b>458</b>. The browser <b>454</b> or one of the other programs <b>456</b> provides a user interface to enable an operator to view, access, or otherwise obtain insurance information provided by the risk generator computing device <b>114</b> or the insurance company providing the dynamic coverage.

0077The risk generator computing device <b>114</b> and the operator computing device <b>108</b> may communicate with each other via communication network <b>110</b>, which may be one or more of a variety of wired or wireless communication networks.

0078The various implementations described above can be combined to provide further embodiments. Aspects of the implementations can be modified, if necessary, to employ further concepts described herein.

0079These and other changes can be made to the implementations in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific implementations disclosed in the specification and the claims, but should be construed to include all possible implementations along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.