This Entity relationship diagram details the database architecture for an airline reservation system, mapping relationships between passengers, flights, aircraft, payments, and tickets. The Passenger entity stores traveler details such as name, contact information, and booking history. Flight operations are managed through the Aircraft and Flight entities, which track plane models, capacities, departure times, and routes.
Reservations are linked to the Payment entity, recording transaction dates, amounts, and methods, while the Ticket entity generates boarding passes with seat assignments, barcodes, and pricing. Airport data, including IATA codes and locations, is stored in the Airport entity, ensuring accurate flight scheduling.