Prompt for the FlightInstanceApp

Please create a React-JS application for the FlightInstanceModule. The application  has to offer the following views for the user interface: 
    1. FlightCrewAssignmentView 
    2. FlightInstanceView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 2 views are defined below.

1. The FlightCrewAssignmentView must contain the following fields: 
    - name: CheckInTime   type: STRING 
    - name: CheckOutTime   type: STRING 
    - name: CrewMember   type: CrewMember 
    - name: DutyRole   type: STRING 
    - name: FlightInstance   type: FlightInstance 
The data source for the [FlightInstance] select control should be loaded from the relative URL: 
    "/FlightInstanceService/flightinstance"   (HTTP-GET) 
The data source for the [CrewMember] select control should be loaded from the relative URL: 
    "/AirlineService/crewmember"   (HTTP-GET) 
An existing FlightCrewAssignment entity should be loaded from the relative URL: 
    "/FlightInstanceService/flightcrewassignment/{id}"   (HTTP-GET) 
If a new FlightCrewAssignment entity has been created, the new entity should be posted to the relative URL: 
    "/FlightInstanceService/flightcrewassignment"   (HTTP-POST) 
If an existing FlightCrewAssignment entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightInstanceService/flightcrewassignment/{id}"   (HTTP-PUT) 
If an existing FlightCrewAssignment entity has to be deleted, the following relative URL should be called: 
    "/FlightInstanceService/flightcrewassignment/{id}"   (HTTP-DELETE)

2. The FlightInstanceView must contain the following fields: 
    - name: ActualArrivalUtc   type: STRING 
    - name: ActualDepartureUtc   type: STRING 
    - name: Aircraft   type: Aircraft 
    - name: FlightSchedule   type: FlightSchedule 
    - name: ScheduledArrivalUtc   type: STRING 
    - name: ScheduledDepartureUtc   type: STRING 
    - name: Status   type: STRING 
The data source for the [FlightSchedule] select control should be loaded from the relative URL: 
    "/FlightNumberService/flightschedule"   (HTTP-GET) 
The data source for the [Aircraft] select control should be loaded from the relative URL: 
    "/AirlineService/aircraft"   (HTTP-GET) 
An existing FlightInstance entity should be loaded from the relative URL: 
    "/FlightInstanceService/flightinstance/{id}"   (HTTP-GET) 
If a new FlightInstance entity has been created, the new entity should be posted to the relative URL: 
    "/FlightInstanceService/flightinstance"   (HTTP-POST) 
If an existing FlightInstance entity has been updated, the modified entity should be sent to the relative URL: 
    "/FlightInstanceService/flightinstance/{id}"   (HTTP-PUT) 
If an existing FlightInstance entity has to be deleted, the following relative URL should be called: 
    "/FlightInstanceService/flightinstance/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following FlightCrewAssignment columns: 
    - column: CheckOutTime 
    - column: DutyRole 
    - column: FlightInstance 
    - column: CheckInTime 
    - column: CrewMember 
The table should have the title "FlightCrewAssignments" und the data must be loaded from the server with the following relative URL: 
    "/FlightInstanceService/flightcrewassignment/flightinstance/{id}" 
Add a HTML table to the view with the following BookingSegment columns: 
    - column: SeatNumber 
    - column: Booking 
    - column: FareClass 
    - column: CheckinStatus 
    - column: FlightInstance 
    - column: SegmentStatus 
The table should have the title "BookingSegments" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/bookingsegment/flightinstance/{id}" 
Add a HTML table to the view with the following LoyaltyTransaction columns: 
    - column: LoyaltyAccount 
    - column: RelatedFlightInstance 
    - column: Miles 
    - column: TransactionType 
    - column: TransactionDate 
    - column: Description 
The table should have the title "LoyaltyTransactions" und the data must be loaded from the server with the following relative URL: 
    "/LoyaltyAccountService/loyaltytransaction/relatedflightinstance/{id}"

Overview