Flight characteristics analysis system, device, and method

Abstract

A flight characteristics analysis system for determining a safe flight score includes a flight characteristics analysis server, including a safe flight model; a flight safety monitoring server; an insurance calculation server, including a premium calculator; and a flight recorder device, including a flight data recorder, a flight data log, and flight data sensors; such that the flight recorder device collects flight data measurements from an aircraft; such that the flight characteristics analysis server compares flight data measurements with the safe flight model for the aircraft, in order to extract a list of safe flight deviations, such that the list of safe flight deviations is used to calculate a safe flight score; such that the flight safety monitoring server stores a plurality of safe flight scores for a plurality of aircraft; and such that insurance calculation server calculates an insurance premium based on the safe flight score.

Claims

1. A flight characteristics analysis system, comprising: a) a flight characteristics analysis server, which comprises: a safe flight model, which comprises aircraft safety models for a plurality of aircraft types, including a corresponding aircraft safety model for an aircraft; whereby the safe flight model stores parameters that indicate flight within a nominal flight envelope per aircraft type in the plurality of aircraft types; and b) a flight recorder device, which is mounted in the aircraft; wherein the flight recorder device collects flight data measurements from the aircraft; wherein the flight characteristics analysis server is configured to compare the flight data measurements with the corresponding aircraft safety model for the aircraft, in order to extract a list of safe flight deviations, such that the list of safe flight deviations is used to calculate a safe flight score.

2. The flight characteristics analysis system of claim 1, wherein the flight characteristics analysis server further comprises: a) a first processor; b) a first non-transitory memory; c) a first input/output component; and d) a flight analyzer, which is configured to compare the flight data measurements with the corresponding aircraft safety model for the aircraft, to extract the list of safe flight deviations, such that the flight analyzer calculates the safe flight score from the list of safe flight deviations.

3. The flight characteristics analysis system of claim 1, further comprising: a flight safety monitoring server; wherein the flight safety monitoring server stores a plurality of safe flight scores for a plurality of aircraft, including the safe flight score for the aircraft, such that the flight safety monitoring server is configured to enable an aviation authority user to perform regional and aircraft type specific analysis of general flight safety, and such that the flight safety monitoring server is configured to enable the aviation authority user to investigate owners and pilots of the aircraft for flight safety violations.

4. The flight characteristics analysis system of claim 1, further comprising: an insurance calculation server; wherein the insurance calculation server is configured to calculate an adjusted insurance premium based on the safe flight score.

5. The flight characteristics analysis system of claim 4, wherein the insurance calculation server further comprises: a) a second processor; b) a second non-transitory memory; c) a second input/output component; and d) a premium calculator, which is configured to calculate the adjusted insurance premium based on the safe flight score; wherein the premium calculator comprises an adjustment function, which calculates a relative safety adjustment factor from an input of the safe flight score; such that the premium calculator calculated the adjusted insurance premium as a standard insurance premium multiplied by the relative safety adjustment factor.

6. The flight characteristics analysis system of claim 2, wherein the flight recorder device further comprises: a) a third processor; b) a third non-transitory memory; c) a third input/output component; d) a flight data sensor assembly, which comprises a plurality of flight sensors; e) a flight data recorder, which is configured to collect the flight data measurements from the aircraft, wherein each flight data measurement comprises: a timestamp; and a list of sensor readings from the flight data sensor assembly; and f) a flight data log, which stores the flight data measurements.

7. The flight characteristics analysis system of claim 6, wherein the plurality of flight sensors comprises: an airspeed sensor, an altitude sensor, a vertical speed sensor, an attitude sensor, a heading sensor, a slip and skid sensor, and a location sensor.

8. The flight characteristics analysis system of claim 6, wherein the safe flight model comprises flight envelope limits, comprising speed limits, climb limits, and descent limits.

9. The flight characteristics analysis system of claim 8, wherein the safe flight model further comprises flight activity limits.

10. The flight characteristics analysis system of claim 9, wherein the safe flight model further comprises a plurality of deviation event definition records.

11. The flight characteristics analysis system of claim 10, wherein each deviation event definition record in the plurality of deviation event definition records, comprises: a) a flight limit type, which is selected from the flight envelope limits and the flight activity limits; b) a flight envelope limit value; c) a limit value type, which is selected from an upper nominal value, a lower nominal value, and a target value; and d) a severity indicator, which indicates a relative deviation severity.

12. The flight characteristics analysis system of claim 11, wherein each deviation event definition record, further comprises: a) a sensor measurement type, which is correlated with the flight limit type; and b) a deviation test procedure, which defines a logical test to determine if a safety deviation has occurred, such that the deviation test procedure processes a flight data measurement in relation to the flight limit type, the flight envelope limit value, the limit value type, and the sensor measurement type, to determine a deviation result.

13. The flight characteristics analysis system of claim 12, wherein the flight analyzer can be configured to determine the list of safe flight deviations by iterating through the flight data measurements, and for each flight data measurement: iterate through all sensor readings in the flight data measurement, and for each sensor reading: identify each corresponding deviation event definition record, such that a type of the sensor reading matches a corresponding sensor measurement type of the corresponding deviation event definition record, and for each corresponding deviation event definition record: execute the deviation test procedure using as input the flight data measurement, to determine if the safety deviation has occurred, and if the safety deviation has occurred: add a safety deviation record to the list of safe flight deviations, wherein the safety deviation record comprises the flight data measurement and the corresponding deviation event definition record.

14. The flight characteristics analysis system of claim 13, wherein the flight analyzer is configured to calculate the safe flight score by iterating through the list of safe flight deviations, aggregating a count of the safe flight deviations, wherein each count is weighted by the severity indicator.

15. The flight characteristics analysis system of claim 1, further comprising: a weighing scale; wherein the weighing scale is connected to the flight recorder device, such that the weighing scale is configured to weigh a pilot user, such that a weight of the pilot user is communicated to the flight recorder device, which transmits the weight, in association with the pilot user and a date and time of the weighing, for storage on the flight characteristics analysis server.

16. A flight characteristics analysis method, comprising: a) collecting a plurality of flight data measurements from an aircraft, such that the flight data measurements are stored in a flight data log; b) determining a list of safe flight deviations, by comparing the flight data measurements with a safe flight model for the aircraft, in order to extract the list of safe flight deviations; c) calculating a safe flight score based on the list of safe flight deviations; and d) calculating an adjusted insurance premium for the aircraft, based on the safe flight score.

17. The flight characteristics analysis method of claim 16, further comprising: calculating a relative safety adjustment factor by using an adjustment function with an input of the safe flight score, such that the adjusted insurance premium is calculated as a standard insurance premium multiplied by the relative safety adjustment factor.

18. The flight characteristics analysis method of claim 16, wherein each flight data measurement in the plurality of flight data measurements comprises: a) a timestamp; and b) a list of sensor readings from the aircraft.

19. The flight characteristics analysis method of claim 18, wherein the safe flight model comprises: a) flight envelope limits, comprising speed limits, climb limits, and descent limits; b) flight activity limits; and c) a plurality of deviation event definition records.

20. The flight characteristics analysis method of claim 19, wherein each deviation event definition record in the plurality of deviation event definition records, comprises: a) a flight limit type, which is selected from the flight envelope limits and the flight activity limits; b) a flight envelope limit value; c) a limit value type, which is selected from an upper nominal value, a lower nominal value, and a target value; and d) a severity indicator, which indicates a relative deviation severity.

21. The flight characteristics analysis method of claim 20, wherein each deviation event definition record, further comprises: a) a sensor measurement type, which is correlated with the flight limit type; and b) a deviation test procedure, which defines a logical test to determine if a safety deviation has occurred, such that the deviation test procedure processes a flight data measurement in relation to the flight limit type, the flight envelope limit value, the limit value type, and the sensor measurement type, to determine a deviation result.

22. The flight characteristics analysis method of claim 21, further comprising: determining the list of safe flight deviations by iterating through the flight data measurements, and for each flight data measurement: iterating through all sensor readings in the flight data measurement, and for each sensor reading: identifying each corresponding deviation event definition record, such that a type of the sensor reading matches a corresponding sensor measurement type of the corresponding deviation event definition record, and for each corresponding deviation event definition record: executing the deviation test procedure using as input the flight data measurement, to determine if the safety deviation has occurred, and if the safety deviation has occurred: add a safety deviation record to the list of safe flight deviations, wherein the safety deviation record comprises the flight data measurement and the corresponding deviation event definition record.

23. The flight characteristics analysis method of claim 22, further comprising: calculating the safe flight score by iterating through the list of safe flight deviations, aggregating a count of the safe flight deviations, wherein each count is weighted by the severity indicator.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG. 1A is a schematic diagram illustrating a system for flight characteristics analysis, according to an embodiment of the invention.

[0028] FIG. 1B is a schematic diagram illustrating a system for flight characteristics analysis, according to an embodiment of the invention.

[0029] FIG. 2A is a schematic diagram illustrating a flight characteristics analysis server, according to an embodiment of the invention.

[0030] FIG. 2B is a schematic diagram illustrating an insurance calculation server, according to an embodiment of the invention.

[0031] FIG. 2C is a schematic diagram illustrating an insurance calculation server, according to an embodiment of the invention.

[0032] FIG. 3 is a schematic diagram illustrating a flight recorder device, according to an embodiment of the invention.

[0033] FIG. 4 is a flowchart illustrating steps that may be followed, in accordance with one embodiment of a method or process of flight characteristics analysis.

[0034] FIG. 5 is a schematic diagram illustrating a flight data log including a plurality of flight data measurements, according to an embodiment of the invention.

[0035] FIG. 6 is a schematic diagram illustrating a safe flight model, according to an embodiment of the invention.

[0036] FIG. 7 is a schematic diagram illustrating a data flow for the system for flight characteristics analysis, according to an embodiment of the invention.

[0037] FIG. 8 is a front view of a mobile device of the system for flight characteristics analysis, according to an embodiment of the invention.

DETAILED DESCRIPTION

[0038] Before describing the invention in detail, it should be observed that the present invention resides primarily in a novel and non-obvious combination of elements and process steps. So as not to obscure the disclosure with details that will readily be apparent to those skilled in the art, certain conventional elements and steps have been presented with lesser detail, while the drawings and specification describe in greater detail other elements and steps pertinent to understanding the invention.

[0039] The following embodiments are not intended to define limits as to the structure or method of the invention, but only to provide exemplary constructions. The embodiments are permissive rather than mandatory and illustrative rather than exhaustive.

[0040] In the following, we describe the structure of an embodiment of a system for flight characteristics analysis system 100a, 100b with reference to FIGS. 1A and 1B, in such manner that like reference numerals refer to like components throughout; a convention that we shall employ for the remainder of this specification.

[0041] In various related embodiments, the flight characteristics analysis system 100 provides a system to help establish safe flying characteristics with the intention of improving flight safety and reducing insurance premiums.

[0042] In an embodiment, as shown in FIGS. 1A, 2, 3, 6 and 7, a flight characteristics analysis system 100a for determining a safe flight score for monitoring of flight safety and for calculation of insurance premiums can include: [0043] a) A flight characteristics analysis server 140, which can include: [0044] i. a safe flight model 212, which includes aircraft safety models 610 for a plurality of aircraft types, including a corresponding aircraft safety model 610 for an aircraft 120, wherein an aircraft type is an aircraft make/model, such as for example a Beechcraft King Air 350i; [0045] b) A flight safety monitoring server 150, which for example can be operated by: [0046] i. An aviation authority, such as the United States Federal Aviation Authority, to assess safe flying behavior; [0047] ii. An aircraft manufacturer, to monitor aircraft usage; [0048] iii. A company to monitor its fleet of aircraft; and/or [0049] iv. An individual owner to store records about previous flights; [0050] c) An insurance calculation server 102, which for example can be operated by an insurance company; and [0051] d) A flight recorder device 104, which is mounted in an aircraft 120; [0052] wherein the flight recorder device 104 collects flight data measurements 510 from the aircraft 120, such that the flight data measurements 510 can be stored in a flight data log 312; [0053] wherein the flight characteristics analysis server 140 can be configured to compare the flight data measurements 510 with a safe flight model 212 for the aircraft 120, in order to extract a list of safe flight deviations 252, such that the list of safe flight deviations 252 is used to calculate a safe flight score 762; [0054] wherein the flight safety monitoring server 150 stores a plurality of safe flight scores for a plurality of aircraft, including the safe flight score 762 for the aircraft, such that an aviation authority user can perform regional and aircraft type specific analysis of general flight safety, and such that the aviation authority can investigate owners and pilots of the aircraft 120 for specific and/or general flight safety violations; [0055] wherein the insurance calculation server 102 can calculate an adjusted insurance premium (for the aircraft 120) based on the safe flight score 762.

[0056] In a related embodiment, as shown in FIG. 2A, a flight characteristics analysis server 140 can include: [0057] a) A first processor 202; [0058] b) A first non-transitory memory 204; [0059] c) A first input/output component 206; [0060] d) A safe flight model 212, which stores parameters that indicate flight within a normal/nominal flight envelope per aircraft type; and [0061] e) A flight analyzer 214, which is configured to compare the flight data measurements with a safe flight model 212 for the aircraft, in order to extract a list of safe flight deviations, such that the flight analyzer 214 calculates a safe flight score from the list of safe flight deviations 510. Flight data measurements 510 can be analyzed on a periodic basis, such as per 1, 5, 10, 40, 160, 200, 500, 1000 flight hours; all connected via [0062] f) A data bus 220.

[0063] In another related embodiment, as shown in FIG. 2B, an insurance calculation server 102 can include: [0064] a) A second processor 202; [0065] b) A second non-transitory memory 204; [0066] c) A second input/output component 206; [0067] d) A premium calculator 210, which can be configured to calculate an insurance premium based on the safe flight score; all connected via [0068] e) A data bus 220.

[0069] In an alternative embodiment, as shown in FIGS. 1B, 2, 3 and 7, a flight characteristics analysis system 100b for determining a safe flight score for calculation of insurance premiums can include: [0070] a) An insurance calculation server 102; and [0071] b) A flight recorder device 104, which is mounted in an aircraft 120; [0072] wherein the flight recorder device 104 collects flight data measurements 510 from the aircraft 120, such that the flight data measurements 510 are stored in a flight data log 312; [0073] wherein the insurance calculation server 102 is configured to compare the flight data measurements 510 with a safe flight model 212 for the aircraft 120, in order to extract a list of safe flight deviations 252, such that the list of safe flight deviations 252 is used to calculate a safe flight score 762; [0074] wherein the insurance calculation server calculates an adjusted insurance premium (for the aircraft 120) based on the safe flight score 762.

[0075] In a related embodiment, as shown in FIG. 2C, an insurance calculation server 162 can include: [0076] a) A processor 202; [0077] b) A non-transitory memory 204; [0078] c) An input/output component 206; [0079] d) A premium calculator 210, which can be configured to calculate an insurance premium based on the safe flight score; [0080] e) A safe flight model 212, which stores parameters that indicate flight within a normal/nominal flight envelope per aircraft type; and [0081] f) A flight analyzer 214, which is configured to compare the flight data measurements with a safe flight model 212 for the aircraft, in order to extract a list of safe flight deviations, such that the flight analyzer 214 calculates a safe flight score from the list of safe flight deviations 510. Flight data measurements 510 can be analyzed on a periodic basis, such as per 1, 5, 10, 40, 160, 200, 500, 1000 flight hours; all connected via [0082] g) A data bus 220.

[0083] In a related embodiment, as shown in FIG. 3, a flight recorder device 104 can include: [0084] a) A third processor 302; [0085] b) A third non-transitory memory 304; [0086] c) An third input/output component 306; [0087] d) A flight data sensor assembly 314, which can include a plurality of flight sensors, which can include: an accelerometer 341, an airspeed sensor 342, an altitude sensor 343 (measuring height above mean sea level), a vertical speed sensor 344, an attitude sensor 345, a heading sensor 346, a slip and skid sensor 347, a location sensor 348; [0088] e) A flight data recorder 310, which can be configured to collect flight data measurements 510 from the flight data sensor assembly 314, wherein each flight data measurement 511 includes a timestamp 512 and a list of sensor readings from the flight data sensor assembly 314, and optionally (or alternatively) other sensor readings or information values obtained from other connected systems, including from the avionics control system 122 and/or the flight planning/information system 124; wherein the sensor readings can include: an airspeed value 513, an altitude value 514 (measuring height above mean sea level or another height metric), a vertical speed value 515, an attitude value 516, a heading value 517, slip and skid values 518, and a location value 519 [0089] f) A flight data log 312, which can store the flight data measurements; and [0090] g) all connected via [0091] h) A data bus 320.

[0092] In related embodiment, as shown in FIG. 6, the safe flight model 212 can include flight envelope limits 620, including speed limits 622, which can include some or all of: [0093] a) V.sub.1: The speed beyond which takeoff should no longer be aborted; [0094] b) V.sub.2: Takeoff safety speed. The speed at which the aircraft may safely be climbed with one engine inoperative; [0095] c) V.sub.2min: Minimum takeoff safety speed; [0096] d) V.sub.3: Flap retraction speed; [0097] e) V.sub.4: Steady initial climb speed. The all engines operating take-off climb speed used to the point where acceleration to flap retraction speed is initiated; [0098] f) V.sub.A: Design maneuvering speed. This is the speed above which it is unwise to make full application of any single flight control (or “pull to the stops”) as it may generate a force greater than the aircraft's structural limitations; [0099] g) V.sub.at: Indicated airspeed at threshold, which is usually equal to the stall speed VS0 multiplied by 1.3 or stall speed VS1g multiplied by 1.23 in the landing configuration at the maximum certificated landing mass, though some manufacturers apply different criteria. If both VS0 and VS1g are available, the higher resulting Vat shall be applied. Also called “approach speed”; [0100] h) V.sub.B Design speed for maximum gust intensity; [0101] i) V.sub.C Design cruise speed, used to show compliance with gust intensity loading; [0102] j) V.sub.cef Critical engine failure speed, i.e. the speed during takeoff where the same distance would be required to either continue the takeoff or abort to a stop; [0103] k) V.sub.D: Design diving speed, the highest speed planned to be achieved in testing; [0104] l) V.sub.DF: Demonstrated flight diving speed, the highest actual speed achieved in testing; [0105] m) V.sub.EF: The speed at which the critical engine is assumed to fail during takeoff; [0106] n) V.sub.F: Designed flap speed. [0107] o) V.sub.FC: Maximum speed for stability characteristics. [0108] p) V.sub.FE: Maximum flap extended speed. [0109] q) V.sub.FTO: Final takeoff speed. [0110] r) V.sub.H: Maximum speed in level flight at maximum continuous power. [0111] s) V.sub.LE: Maximum landing gear extended speed. This is the maximum speed at which a retractable gear aircraft should be flown with the landing gear extended; [0112] t) V.sub.LO: Maximum landing gear operating speed. This is the maximum speed at which the landing gear on a retractable gear aircraft should be extended or retracted; [0113] u) V.sub.LOF: Lift-off speed; [0114] v) V.sub.MC: Minimum control speed. The minimum speed at which the aircraft is still controllable with the critical engine inoperative; [0115] w) V.sub.MCA: Minimum control speed air. The minimum speed that the aircraft is still controllable with the critical engine inoperative while the aircraft is airborne; [0116] x) V.sub.MCG: Minimum control speed ground. The minimum speed that the aircraft is still controllable with the critical engine inoperative while the aircraft is on the ground; [0117] y) V.sub.MCL: Minimum control speed in the landing configuration with one engine inoperative; [0118] z) V.sub.MO: Maximum operating limit speed; [0119] aa) V.sub.MU: Minimum unstick speed; [0120] bb) V.sub.NE: Never exceed speed; [0121] cc) V.sub.NO: Maximum structural cruising speed or maximum speed for normal operations; [0122] dd) V.sub.O: Maximum operating maneuvering speed; [0123] ee) V.sub.R: Rotation speed. The speed at which the pilot begins to apply control inputs to cause the aircraft nose to pitch up, after which it will leave the ground.[Note 1] [0124] ff) V.sub.Ref: Landing reference speed or threshold crossing speed; [0125] gg) V.sub.S: Stall speed or minimum steady flight speed for which the aircraft is still controllable; [0126] hh) V.sub.S0: Stall speed or minimum flight speed in landing configuration; [0127] ii) V.sub.S1: Stall speed or minimum steady flight speed for which the aircraft is still controllable in a specific configuration; [0128] jj) V.sub.SR: Reference stall speed; [0129] kk) V.sub.SR0: Reference stall speed in landing configuration; [0130] ll) V.sub.SR1: Reference stall speed in a specific configuration; [0131] mm) V.sub.SW: Speed at which the stall warning will occur; and/or [0132] nn) V.sub.TOSS: Category A rotorcraft takeoff safety speed.

[0133] In related embodiment, the flight envelope limits 620 can further include climb 624 and descent limits 626, which for example can include some or all of: [0134] a) Maximum descent rate, for example measured in feet per minute; [0135] b) Maximum ascent/climb rate, for example measured in feet per minute; [0136] c) Maximum positive angle of attack; and/or [0137] d) Maximum negative angle of attack.

[0138] In related embodiment, the safe flight model 212 can include flight activity limits 630, which for example can include some or all of: [0139] a) Flight into severe weather; [0140] b) Flight close to ground; [0141] c) Flight into instrument meteorological conditions (IMC) without an IFR clearance; [0142] d) Flight into instrument meteorological conditions (IMC) without an instrument rating; and/or [0143] e) Etc.

[0144] In a related embodiment, the safe flight model 212 can include a plurality of deviation event definition records 640, wherein each deviation event definition record 641, can include: [0145] a) A flight envelope/activity limit type 642, also called a flight limit type 642, as defined above, such as minimum control speed, maximum descent rate, etc.; [0146] b) A flight envelope limit value 643; [0147] c) A limit value type 644, which for example can be set to either upper nominal value (which can also be called Safe Maximum) or lower nominal value (which can also be called Safe Minimum); or target nominal value (which can also be called Safe Target Value), such that: [0148] i. For upper nominal value/“Maximum”: an actual sensor reading above the flight envelope limit value indicates a safe flight deviation; [0149] ii. For lower nominal value/“Minimum”: an actual sensor reading below the flight envelope limit value indicates a safe flight deviation; [0150] iii. For target nominal value: an actual sensor reading positive/negative difference to the flight envelope limit value indicates a safe flight deviation, which for example can be established within a predetermined tolerance, such as by percentage or absolute value deviation; [0151] d) A severity indicator 646, which can be a numerical value, which indicates a relative deviation severity, which can be used to weight deviations in order to determine an accumulated safe slight score. [0152] e) A sensor measurement type 648, which is correlated with the flight envelope/activity limit type 642, wherein the sensor measurement type 648 corresponds to a sensor available from the flight data sensor assembly 314. A speed limit will for example correlate with an airspeed sensor 342 in the flight data sensor assembly 314; [0153] f) A deviation test procedure 649, which can be a test script or test definition which defines a logical test to determine if a safety deviation has occurred, such that the deviation test procedure processes a flight data measurement in relation to the flight envelope/activity limit type, the flight envelope limit value, limit category, and sensor measurement type, in order to determine a deviation result, which can for example be “false” or “true”; and

[0154] In a related embodiment, the premium calculator 210 can include a premium adjustment function 211, which calculates a relative safety adjustment factor 764 (as a factor such as 0.9 or 1.1) from an input of the safe flight score; such that the premium calculator 210 calculates the adjusted insurance premium 774 as a standard insurance premium 772 (for the specific aircraft make/model and geographical region) multiplied by the relative safety adjustment factor 764. The adjustment function 211 can for example be implemented as a table lookup in an adjustment table, with each row including a safe flight score value 762 and a corresponding relative safety adjustment factor 764.

[0155] In another related embodiment, the flight analyzer 214 can be configured to determine the list of safe flight deviations 640 by iterating through the flight data measurements 510, and for each flight data measurement 511: [0156] a) Iterate through all sensor readings 513, 514, 515, 516, 517, 518, 519 in the flight data measurement 511, and for each sensor reading 513, 514, 515, 516, 517, 518, 519: [0157] i. Identify each corresponding deviation event definition record 641, such that a type of the sensor reading matches a corresponding sensor measurement type 648 of the corresponding deviation event definition record 641, and for each corresponding deviation event definition record 641: [0158] execute the deviation test procedure 649 using as input the flight data measurement 511, to determine if a safety deviation has occurred, and if a safety deviation has occurred: [0159] add a safety deviation record 751 to the list of safe flight deviations 750, wherein the safety deviation record 751 can include the flight data measurement 511 and the corresponding deviation event definition record 641.

[0160] In another related embodiment, the flight analyzer 214 can be configured to calculate the safe flight score 762 by iterating through the list of safe flight deviations 750, aggregating a count of the safe flight deviations 751, wherein each count is weighted by the severity indicator 646. Alternatively, the safe flight score 762 can be calculated as an aggregation of all severity indicators 646 in the list of safe flight deviations 750.

[0161] In a related embodiment, as shown in FIGS. 1A and 1B, a mobile device 110, can communicate with the flight recorder device 104, for example via a wireless connection, such as a cellular connection, WIFI™, or BLUETOOTH™, to enable a user 182 to review data on the flight recorder device 104, or to configure the flight recorder device 104.

[0162] In a further related embodiment, the mobile device 110 can connect to one or more flight recorder devices 104. FIG. 5 shows a flight recorder devices 104, wherein a graphical user interface of the mobile device 110 indicates that the mobile device 110 is connected to a first flight recorder devices 104, and provides an option for connecting additional flight recorder devices 104.

[0163] In related embodiments, the flight recorder device 104 can be configured to be universally compatible with any aircraft/airframe, as well as other applications 124 and systems 122. The flight recorder device 104 can be manufactured using inexpensive components, as well as adding connectivity previously not interfaced equipment, in order to enable storage of a more complete flight record. Our system is also self-contained to reduce complexity to the end user as well as creating a device with minimal change to application the system is installed in.

[0164] In related embodiment, data can be brought in from the various system receivers or via the mobile device 110, and is processed and recorded onto the devices storage system. Once the device has a stable connection to the off-device storage suite it then offloads the data using SIM card cellular data or a reachable WIFI network.

[0165] In a related embodiment, the flight recorder device 104, can be connected with an avionics control system 122 of the aircraft 120, such as for example a GARMIN G1000™ system 122, such that some sensor measurement values can be obtained in communication with the avionics control system 122, or sensor measurement values from the flight data sensor assembly/system 314 of the flight recorder device 104 can be compared with corresponding sensor measurement values from the avionics control system 122 to trigger an inflight deviation alarm, if a difference exceeds a predetermined variation threshold. The flight recorder device 104, can be connected with an avionics control system 122 via an onboard databus 126, such as for example ARINC 429, also called Mark 33 Digital Information Transfer System (DITS), and can use an open or proprietary application programming interface (API).

[0166] In another related embodiment, the flight recorder device 104, can be connected with a flight planning/information system 124 of the aircraft 120, such as for example a FOREFLIGHT™ system 124 or an ADS-B system, such that the flight recorder device 104 for example can obtain location information, map information, weather information, etc., from the flight planning/information system 124.

[0167] In yet a related embodiment, the flight characteristics analysis system 100a, 100b can further include: [0168] An enterprise resource planning system 130, which can be an insurance management system 130, such that the insurance calculation server is connected with the insurance management system 130, such that the insurance calculation can lookup insurance information and communicate with the enterprise resource planning system 130 in order to create an insurance policy with the calculated insurance premium.

[0169] In yet another related embodiment, the flight characteristics analysis system 100a, 100b can further include: [0170] A weighing scale 170, which is connected to the flight recorder device 104, such that the weighing scale 170 can be configured to weigh a pilot user 182, such that a weight of the pilot user 182 can be communicated to the flight recorder device 104, which transmits the weight, in association with the pilot user 182 and a date and time of the weighing, for storage on the flight characteristics analysis server 140.

[0171] In a related embodiment, the flight recorder device 104 can include: [0172] a) A cellular wireless transceiver; [0173] b) A SIM card; [0174] c) A WiFi Module; [0175] d) A crash resistant enclosure; [0176] e) Open API for 3rd party integration; [0177] f) Uploads to cloud rescue services, using GPS, Cellular triangulation and last known location; [0178] g) Location ping out to selected users; [0179] h) Multiple voltage power supply, including 5V, 12V, and/or 24V; [0180] i) Bluetooth for smartphone app connection; [0181] j) Battery Backup supply, which for example can support 30 minutes operation at nominal load; [0182] k) Port for external GPS connection; [0183] l) Setup for over the air updates via bluetooth phone link or sim/sd card downloads; [0184] m) A G-Meter; [0185] n) A biometric authenticator, such as a fingerprint reader, facial recognizer, or other biometric function for matching the flight data with a pilot; [0186] o) ADSB in for traffic and weather recording/analysis; and/or [0187] p) Internal or external integration with other flight monitoring or flight safety components or systems 122, 124.

[0188] In related embodiments, the mobile device 110 can include configurations as: [0189] a) A web application, executing in a Web browser; [0190] b) A tablet app, executing on a tablet device, such as for example an ANDROID™ or IOS™ tablet device; [0191] c) A mobile app, executing on a mobile device, such as for example an ANDROID™ phone or IPHONE™, or any wearable mobile device; [0192] d) A desktop application, executing on a personal computer, or similar device; or [0193] e) An embedded application, executing on a processing device, such as for example a smart TV, a game console or other system.

[0194] It shall be understood that an executing instance of an embodiment of the flight characteristics analysis system 100a, 100b, as shown in FIGS. 1A and 1B, can include a plurality of flight recorder devices 104 (each mounted in a separate aircraft 120), which can each connect to an insurance calculation server 102, 162.

[0195] An executing instance of an embodiment of the system for flight characteristics analysis system 100a, 100b, as shown in FIGS. 1A and 1B, can similarly include a plurality of insurance calculation servers 102, 162.

[0196] Further, it shall similarly be understood that an executing instance of an embodiment of the flight characteristics analysis system 100a, 100b, as shown in FIGS. 1A and 1B, can include a plurality of mobile devices 110, which are each tied to one or more users 182.

[0197] In an embodiment, as illustrated in FIG. 4, a method for flight characteristics analysis 400, can include: [0198] a) Collecting flight data measurements 402 from an aircraft 120, such that the flight data measurements are stored in a flight data log 312; [0199] b) Determining a list of safe flight deviations 404, by comparing the flight data measurements with a safe flight model for the aircraft, in order to extract the list of safe flight deviations; [0200] c) Calculating a safe flight score 406 based on the list of safe flight deviations; and [0201] d) Calculating an insurance premium 408 for the aircraft 120, based on the safe flight score.

[0202] FIGS. 1, 2, 3 and 4 are block diagrams and flowcharts, methods, devices, systems, apparatuses, and computer program products according to various embodiments of the present invention. It shall be understood that each block or step of the block diagram, flowchart and control flow illustrations, and combinations of blocks in the block diagram, flowchart and control flow illustrations, can be implemented by computer program instructions or other means. Although computer program instructions are discussed, an apparatus or system according to the present invention can include other means, such as hardware or some combination of hardware and software, including one or more processors or controllers, for performing the disclosed functions.

[0203] In this regard, FIGS. 1A, 1B, 2A, 2B, 2C and 3 depict the computer devices of various embodiments, each containing several of the key components of a general-purpose computer by which an embodiment of the present invention may be implemented. Those of ordinary skill in the art will appreciate that a computer can include many components. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment for practicing the invention. The general-purpose computer can include a processing unit and a system memory, which may include various forms of non-transitory storage media such as random access memory (RAM) and read-only memory (ROM). The computer also may include nonvolatile storage memory, such as a hard disk drive, where additional data can be stored.

[0204] FIGS. 1A and 1B show a depiction of an embodiment of the flight characteristics analysis system 100a, 100b, including the insurance calculation server 102, 162 and the flight recorder device 104. In this relation, a server shall be understood to represent a general computing capability that can be physically manifested as one, two, or a plurality of individual physical computing devices, located at one or several physical locations. A server can for example be manifested as a shared computational use of one single desktop computer, a dedicated server, a cluster of rack-mounted physical servers, a datacenter, or network of datacenters, each such datacenter containing a plurality of physical servers, or a computing cloud, such as AMAZON EC2™ or MICROSOFT AZURE™.

[0205] It shall be understood that the above-mentioned components of the insurance calculation server 102, 162 and the flight recorder device 104 are to be interpreted in the most general manner.

[0206] For example, the processors 202 302 can each respectively include a single physical microprocessor or microcontroller, a cluster of processors, a datacenter or a cluster of datacenters, a computing cloud service, and the like.

[0207] In a further example, the non-transitory memory 204 and the non-transitory memory 304 can each respectively include various forms of non-transitory storage media, including random access memory and other forms of dynamic storage, and hard disks, hard disk clusters, cloud storage services, and other forms of long-term storage. Similarly, the input/output 206 and the input/output 306 can each respectively include a plurality of well-known input/output devices, such as screens, keyboards, pointing devices, motion trackers, communication ports, and so forth.

[0208] Furthermore, it shall be understood that the insurance calculation server 102 and the flight recorder device 104 can each respectively include a number of other components that are well known in the art of general computer devices, and therefore shall not be further described herein. This can include system access to common functions and hardware, such as for example via operating system layers such as WINDOWS™, LINUX™, and similar operating system software, but can also include configurations wherein application services are executing directly on server hardware or via a hardware abstraction layer other than a complete operating system.

[0209] An embodiment of the present invention can also include one or more input or output components, such as a mouse, keyboard, monitor, and the like. A display can be provided for viewing text and graphical data, as well as a user interface to allow a user to request specific operations. Furthermore, an embodiment of the present invention may be connected to one or more remote computers via a network interface. The connection may be over a local area network (LAN) wide area network (WAN), and can include all of the necessary circuitry for such a connection.

[0210] In a related embodiment, the flight recorder device 104 communicates with the insurance calculation server 102, 162 over a network 106, which can include the general Internet, a Wide Area Network or a Local Area Network, or another form of communication network, transmitted on wired or wireless connections. Wireless networks can for example include Ethernet, Wi-Fi, BLUETOOTH™, ZIGBEE™, and NFC. The communication can be transferred via a secure, encrypted communication protocol.

[0211] Typically, computer program instructions may be loaded onto the computer or other general-purpose programmable machine to produce a specialized machine, such that the instructions that execute on the computer or other programmable machine create means for implementing the functions specified in the block diagrams, schematic diagrams or flowcharts. Such computer program instructions may also be stored in a computer-readable medium that when loaded into a computer or other programmable machine can direct the machine to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means that implement the function specified in the block diagrams, schematic diagrams or flowcharts.

[0212] In addition, the computer program instructions may be loaded into a computer or other programmable machine to cause a series of operational steps to be performed by the computer or other programmable machine to produce a computer-implemented process, such that the instructions that execute on the computer or other programmable machine provide steps for implementing the functions specified in the block diagram, schematic diagram, flowchart block or step.

[0213] Accordingly, blocks or steps of the block diagram, flowchart or control flow illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block or step of the block diagrams, schematic diagrams or flowcharts, as well as combinations of blocks or steps, can be implemented by special purpose hardware-based computer systems, or combinations of special purpose hardware and computer instructions, that perform the specified functions or steps.

[0214] As an example, provided for purposes of illustration only, a data input software tool of a search engine application can be a representative means for receiving a query including one or more search terms. Similar software tools of applications, or implementations of embodiments of the present invention, can be means for performing the specified functions. For example, an embodiment of the present invention may include computer software for interfacing a processing element with a user-controlled input device, such as a mouse, keyboard, touch screen display, scanner, or the like. Similarly, an output of an embodiment of the present invention may include, for example, a combination of display software, video card hardware, and display hardware. A processing element may include, for example, a controller or microprocessor, such as a central processing unit (CPU), arithmetic logic unit (ALU), or control unit.

[0215] Here has thus been described a multitude of embodiments of the . . . device, and methods related thereto, which can be employed in numerous modes of usage.

[0216] The many features and advantages of the invention are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the invention, which fall within the true spirit and scope of the invention.

[0217] For example, alternative embodiments can reconfigure or combine the components of the insurance calculation server 102 and the flight recorder device 104. The components of the insurance calculation server 102 can be distributed over a plurality of physical, logical, or virtual servers. Some components of the flight recorder device 104 can be configured to operate in the insurance calculation server 102. Alternatively, parts or all of the components of the insurance calculation server 102 can be configured to operate in the flight recorder device 104.

[0218] Many such alternative configurations are readily apparent, and should be considered fully included in this specification and the claims appended hereto. Accordingly, since numerous modifications and variations will readily occur to those skilled in the art, the invention is not limited to the exact construction and operation illustrated and described, and thus, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention.