Prompt for the FlightApp

Please create a React-JS application for the FlightModule. The application  has to offer the following views for the user interface: 
    1. AirlineView 
    2. AirportView 
    3. AlertView 
    4. FlightView 
    5. RouteSegmentView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The AirlineView must contain the following fields: 
    - name: Active   type: BOOL 
    - name: Callsign   type: STRING 
    - name: Country   type: STRING 
    - name: IataCode   type: STRING 
    - name: IcaoCode   type: STRING 
    - name: LogoUrl   type: STRING 
    - name: Name   type: STRING 
An existing Airline entity should be loaded from the relative URL: 
    "/FlightService/airline/{id}"   (HTTP-GET) 
If a new Airline entity has been created, the new entity should be posted to the relative URL: 
    "/FlightService/airline"   (HTTP-POST) 
If an existing Airline entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightService/airline/{id}"   (HTTP-PUT) 
If an existing Airline entity has to be deleted, the following relative URL should be called: 
    "/FlightService/airline/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Flight columns: 
    - column: ActualArrivalUtc 
    - column: ActualDepartureUtc 
    - column: DistanceNm 
    - column: LastPositionTimeUtc 
    - column: Status 
    - column: Live 
    - column: Callsign 
    - column: ArrivalAirport 
    - column: DepartureAirport 
    - column: Aircraft 
    - column: ScheduledArrivalUtc 
    - column: Airline 
    - column: ScheduledDepartureUtc 
    - column: Number 
    - column: ProgressPercent 
The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/flight/airline/{id}" 
Add a HTML table to the view with the following Aircraft columns: 
    - column: Airline 
    - column: DeliveryDate 
    - column: AgeYears 
    - column: SerialNumber 
    - column: AircraftModel 
    - column: Registration 
    - column: ModeS 
The table should have the title "Aircrafts" und the data must be loaded from the server with the following relative URL: 
    "/AircraftService/aircraft/airline/{id}"

2. The AirportView must contain the following fields: 
    - name: City   type: STRING 
    - name: Country   type: STRING 
    - name: ElevationFt   type: INT 
    - name: IataCode   type: STRING 
    - name: IcaoCode   type: STRING 
    - name: Latitude   type: DOUBLE 
    - name: Longitude   type: DOUBLE 
    - name: Name   type: STRING 
    - name: TimeZone   type: STRING 
An existing Airport entity should be loaded from the relative URL: 
    "/FlightService/airport/{id}"   (HTTP-GET) 
If a new Airport entity has been created, the new entity should be posted to the relative URL: 
    "/FlightService/airport"   (HTTP-POST) 
If an existing Airport entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightService/airport/{id}"   (HTTP-PUT) 
If an existing Airport entity has to be deleted, the following relative URL should be called: 
    "/FlightService/airport/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Flight columns: 
    - column: ActualArrivalUtc 
    - column: ActualDepartureUtc 
    - column: DistanceNm 
    - column: LastPositionTimeUtc 
    - column: Status 
    - column: Live 
    - column: Callsign 
    - column: ArrivalAirport 
    - column: DepartureAirport 
    - column: Aircraft 
    - column: ScheduledArrivalUtc 
    - column: Airline 
    - column: ScheduledDepartureUtc 
    - column: Number 
    - column: ProgressPercent 
The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/flight/arrivalairport/{id}" 
Add a HTML table to the view with the following Flight columns: 
    - column: ActualArrivalUtc 
    - column: ActualDepartureUtc 
    - column: DistanceNm 
    - column: LastPositionTimeUtc 
    - column: Status 
    - column: Live 
    - column: Callsign 
    - column: ArrivalAirport 
    - column: DepartureAirport 
    - column: Aircraft 
    - column: ScheduledArrivalUtc 
    - column: Airline 
    - column: ScheduledDepartureUtc 
    - column: Number 
    - column: ProgressPercent 
The table should have the title "Flights" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/flight/departureairport/{id}"

3. The AlertView must contain the following fields: 
    - name: Active   type: BOOL 
    - name: CreatedAtUtc   type: DATE 
    - name: Flight   type: Flight 
    - name: TriggerConditionJson   type: STRING 
    - name: Type   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [Flight] select control should be loaded from the relative URL: 
    "/FlightService/flight"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Alert entity should be loaded from the relative URL: 
    "/FlightService/alert/{id}"   (HTTP-GET) 
If a new Alert entity has been created, the new entity should be posted to the relative URL: 
    "/FlightService/alert"   (HTTP-POST) 
If an existing Alert entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightService/alert/{id}"   (HTTP-PUT) 
If an existing Alert entity has to be deleted, the following relative URL should be called: 
    "/FlightService/alert/{id}"   (HTTP-DELETE)

4. The FlightView must contain the following fields: 
    - name: ActualArrivalUtc   type: DATE 
    - name: ActualDepartureUtc   type: DATE 
    - name: Aircraft   type: Aircraft 
    - name: Airline   type: Airline 
    - name: ArrivalAirport   type: Airport 
    - name: Callsign   type: STRING 
    - name: DepartureAirport   type: Airport 
    - name: DistanceNm   type: DOUBLE 
    - name: LastPositionTimeUtc   type: DATE 
    - name: Live   type: BOOL 
    - name: Number   type: STRING 
    - name: ProgressPercent   type: DOUBLE 
    - name: ScheduledArrivalUtc   type: DATE 
    - name: ScheduledDepartureUtc   type: DATE 
    - name: Status   type: STRING 
The data source for the [DepartureAirport] select control should be loaded from the relative URL: 
    "/FlightService/airport"   (HTTP-GET) 
The data source for the [ArrivalAirport] select control should be loaded from the relative URL: 
    "/FlightService/airport"   (HTTP-GET) 
The data source for the [Airline] select control should be loaded from the relative URL: 
    "/FlightService/airline"   (HTTP-GET) 
The data source for the [Aircraft] select control should be loaded from the relative URL: 
    "/AircraftService/aircraft"   (HTTP-GET) 
An existing Flight entity should be loaded from the relative URL: 
    "/FlightService/flight/{id}"   (HTTP-GET) 
If a new Flight entity has been created, the new entity should be posted to the relative URL: 
    "/FlightService/flight"   (HTTP-POST) 
If an existing Flight entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightService/flight/{id}"   (HTTP-PUT) 
If an existing Flight entity has to be deleted, the following relative URL should be called: 
    "/FlightService/flight/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Alert columns: 
    - column: Type 
    - column: CreatedAtUtc 
    - column: Active 
    - column: Flight 
    - column: TriggerConditionJson 
    - column: UserAccount 
The table should have the title "Alerts" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/alert/flight/{id}" 
Add a HTML table to the view with the following FlightPosition columns: 
    - column: AltitudeFt 
    - column: Source 
    - column: Receiver 
    - column: GroundSpeedKt 
    - column: TrackDeg 
    - column: Flight 
    - column: OnGround 
    - column: TimestampUtc 
    - column: Longitude 
    - column: VerticalSpeedFpm 
    - column: Latitude 
The table should have the title "FlightPositions" und the data must be loaded from the server with the following relative URL: 
    "/ReceiverService/flightposition/flight/{id}" 
Add a HTML table to the view with the following RouteSegment columns: 
    - column: Flight 
    - column: Longitude 
    - column: PlannedSpeedKt 
    - column: SequenceNumber 
    - column: PlannedAltitudeFt 
    - column: Latitude 
The table should have the title "RouteSegments" und the data must be loaded from the server with the following relative URL: 
    "/FlightService/routesegment/flight/{id}"

5. The RouteSegmentView must contain the following fields: 
    - name: Flight   type: Flight 
    - name: Latitude   type: DOUBLE 
    - name: Longitude   type: DOUBLE 
    - name: PlannedAltitudeFt   type: INT 
    - name: PlannedSpeedKt   type: INT 
    - name: SequenceNumber   type: INT 
The data source for the [Flight] select control should be loaded from the relative URL: 
    "/FlightService/flight"   (HTTP-GET) 
An existing RouteSegment entity should be loaded from the relative URL: 
    "/FlightService/routesegment/{id}"   (HTTP-GET) 
If a new RouteSegment entity has been created, the new entity should be posted to the relative URL: 
    "/FlightService/routesegment"   (HTTP-POST) 
If an existing RouteSegment entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightService/routesegment/{id}"   (HTTP-PUT) 
If an existing RouteSegment entity has to be deleted, the following relative URL should be called: 
    "/FlightService/routesegment/{id}"   (HTTP-DELETE)