The introduction of Very Light Jets (VLJ) worldwide in the modern aviation environment represents a potential challenge in terms of safety and investigation. The VLJs are intended to be flown by a single pilot and carry a high level of automation, with state of the art glass cockpits and extensive use of onboard software. Although in some cases it is not even mandatory for them to carry a CVR/FDR, some manufacturers choose to provide these recorders for their VLJ in order to improve the safety and investigation resources. The FDR will be more limited than the ones used in commercial aviation, but, nonetheless, will open the possibility for some important safety monitoring programs, like Flight Operational Quality Assurance (FOQA). This study describes modern VLJs and recorder systems, then covers the selection of the parameters for the FDR dataframe of a VLJ and proposes the structure of a FOQA program for this type of aircraft, taking as example the EMBRAER Phenom 100. The events to be monitored by this program are summarized and applied to real incidents and accidents that occurred with VLJs in order to show how FOQA can help preventing them.

This study describes the development of a tool for the computation of the aircraft trajectory when it gets involved in a runway overrun incident. This tool performs its computations based on the FDR (Flight Data Recorder) in-flight data. The result of this study is a useful tool for the investigation of such events because it may help in the identification of the involved contributing factors. The requirements for the tool are defined and the tool development follows the proposed requirements. There are several ways to calculate the trajectory based on the FDR data. In this study, three reconstruction methods are described and one of these methods is implemented in the tool. Several FDR parameters are used to create a reconstitution of aircraft';s position from the final approach to the touchdown point on the runway surface. Finally, the tool';s results are validated based on a proposed methodology and the conclusion discusses whether the tool';s requirements are effectively achieved.