table: crew_category column name sample value *id 1
table: crew_category column name sample value *id 1 description Pilot To avoid columns like pilot_last_name, copilot_first_name, we form a crew_category table. See also the related flight_crew table later in this chapter. table: ticket_refundability column name sample value *id 1 description non-refundable table: flight_status column name sample value *id 1 description boarding table: event column name sample value *id 1 description repair If we need to include other types of events in the model, this event table will have to be renamed as something more precise like plane_event, and a new name will be needed for our current plane_event table that is used to associate an event with a plane. Themed Tables These tables are more comprehensive than the code tables. Each one refers to a specific theme that needs more columns than a simple code table. table: plane column name sample value *id 302 airline_id 1 brand_id 1 model_id 2 description Charlie This table identifies which aircraft belongs to which airline, with the description being an internal means of describing this particular aircraft within the airline. Other fields like an aircraft serial number can be added here.