FlightRecorder implements a SQL-based aircraft sightings logbook. An ASP.NET WebAPI provides access to the business logic and data access layer while an ASP.NET MVC UI provides the user interface.
Each sighting consists of the following data:
- Flight details
- Flight number
- Embarkation airport IATA code
- Destination IATA code
- Airline
- Aircraft details
- Registration details
- Manufacturer
- Model
- Sighting details
- Date
- Altitude when sighted
- Location
A register of airport codes by country is used to validate airport IATA codes.
Sightings may be searched by:
- Route, specified as airport IATA codes
- Flight number
- Airline name
- Aircraft registration number
- Date
The following reports can be generated and exported to CSV format files:
- Airline statistics
- Flights by month
- Location statistics
- Manufacturer statistics
- Aircraft model statistics
The following data can be exported in CSV format:
- Sightings
- Airport code and country list
Please see the Wiki for configuration details and the user guide.
- Dave Walker - Initial work - LinkedIn
Implementation of authentication using JWT in the REST API is based on the following tutorial:
- https://github.com/cornflourblue/aspnet-core-3-jwt-authentication-api
- https://jasonwatmore.com/post/2019/10/11/aspnet-core-3-jwt-authentication-tutorial-with-example-api#users-controller-cs
The Flight Recorder MVC project uses the Gijgo JavaScript controls library:
To file issues or suggestions, please use the Issues page for this project on GitHub.
This project is licensed under the MIT License - see the LICENSE file for details