Giant Big Stik R/C UAV computer model development in JSBSim for sense and avoid applications

Oihane Cereceda, Luc Rolland, Siu O'Young

    Research output: Contribution to journalArticlepeer-review

    5 Citations (Scopus)
    161 Downloads (Pure)

    Abstract

    Open-source aerospace simulation packages often lack unmanned aerial vehicles (UAVs) models, limiting the study of their interaction with other elements in the airspace. These events, which are a consequence of encounters between manned and unmanned aircraft, have recently attracted interest due to the uncertainties created by UAVs in real environments. In this paper, a fit-for-purpose flight dynamics model specific for sense and avoid (SAA) strategies in near mid-air collision scenarios is developed based on existing model development practices and adjusted from flight data. The Giant Big Stik is recognized as the representative aircraft for testing SAA manoeuvres due to its capabilities. The simulation platform is based on the JSBSim open-source flight dynamics model, and the SAA application is carried out following the current regulations and flight recommendations for UAVs in Canada. Through this methodology, the error between the real and the computer model is reduced in every step that is minimal for the SAA application. The relevance of this paper is also shown in future applications, where this model will be incorporated into more complex simulations with manned aircraft for the study of avoidance manoeuvres that will serve the safe integration of UAVs into the airspace.
    Original languageEnglish
    Article number48
    JournalDrones
    Volume3
    Issue number2
    DOIs
    Publication statusPublished - 18 Jun 2019

    Keywords

    • JSBSim flight dynamics model
    • UAV computer model design
    • UAV simulation packages
    • UAV modelling tutorial

    Fingerprint

    Dive into the research topics of 'Giant Big Stik R/C UAV computer model development in JSBSim for sense and avoid applications'. Together they form a unique fingerprint.

    Cite this