Create an Entity Relationship Diagram.

A small airport wishes to maintain a database about its flights instructors, trainees, and the flights that the trainees perform under the guidance of the flight instructors.

The airport keeps the following information about the trainees: unique trainee ID, first and last names, DOB, contact phone #.

The airport keeps the following information about its flight instructors: unique license #, first and last names, DOB, contact phone #.

The airport owns several planes. For every plane the airport keeps its serial #, maker name, date it was produced, date the plane was last serviced and the comments regarding the plane condition that were left after the last service. The airport has only small two-seat planes.

The flights that trainees complete on the airport planes under the guidance of the airport flight instructors have unique flight IDs, destination, departure time (that includes day and time), and planned departure time (that include day and time).

Every pilot is required to go to medical check-ups performed by the doctors approved by the airport. For the approved doctors the airport keeps the information about their medical ID, first and last names, office location, office phone number. Before a new flight instructor is hired by the airport, this instructor needs to complete a check-up with one of the approved doctors.

Each check-up is completed by one doctor.

For each check-up the airport stores the following information: unique record number, date, grade assigned to the pilot by the doctor, and the comments left by the doctor.

Some of the approved doctors are inconveniently located far from the airport. And, though the pilots do not go to these doctors for check-ups, the airport still maintains the information about these doctors (in case they move closer to the airport or a flight instructor is hired who lives next to the office of one of such doctors).