SFO Flight Operations
City of San Francisco
@usgov.city_of_san_francisco_sfo_flight_operations
City of San Francisco
@usgov.city_of_san_francisco_sfo_flight_operations
A. SUMMARY San Francisco International Airport (SFO) keeps track of historical flight operations, also known as aircraft RADAR data for analysis and reporting. B. HOW THE DATASET IS CREATED Details of flights from the Federal Aviation Administration’s National Offload Program are processed into SFO’s Airport Noise and Operations Management System (ANOMS) where it is correlated with noise reports from the communities and to noise levels collected from noise monitor sites on the San Francisco Peninsula. In ANOMS, various analysis gates (imaginary vertical curtain in space) are used to identify which route flights flew departing and arriving SFO. It serves to quantify, analyze, respond to noise concerns, and report on Runway Use and various programs to reduce aircraft noise in communities surrounding SFO. C. UPDATE PROCESS Data is available starting in August 2019 and will be updated monthly. D. HOW TO USE THIS DATASET It is important to note, that this dataset is of flights departing and landing at SFO only and not flight activities associated with other airports in the Bay Area region. This information is the data source used to produce the Flight Operations sections (pages 3-5) of the Airport Director’s Report. These reports are presented at the SFO Airport Community Roundtable Meetings and available online at https://noise.flysfo.com/reports/?category=airport-directors-report E. RELATED DATASETS Unique Flight Operations - This filtered view contains unique records of flight operations. For example, one record for a flight that departed SFO or one record for a flight that landed at SFO. Arrival and Departure Routes - This filtered view contains records of flights with details of analysis gate(s) the aircraft flight track penetrates, to derive which route was used to depart and land at SFO. This dataset contains Operations and Arrival and Departure Routes joined on operation_number. The field gate_penetration is derived by ordering the arrival and departure routes for each operation over gate_penetration_time. Unique_identifier is then created by joining operation_number and gate_penetration. Other provided datasets are Aircraft Noise Reports, Late Night Aircraft Departures, Air Carrier Runway Use, and Late Night Preferential Runway Use, Aircraft Noise Climates, and Noise Exceedance Rating. Please contact the Noise Abatement Office at NoiseAbatementOffice@flysfo.com for any questions regarding this data. Date created: November 17, 2023
Organization: City of San Francisco
Last updated: 2023-11-24T14:12:05.529397
CREATE TABLE table_1 (
"unique_identifier" VARCHAR,
"operation_no" BIGINT,
"flight_date_time" VARCHAR,
"year" BIGINT,
"month" BIGINT,
"hour" BIGINT,
"corr_id" BIGINT,
"operation_type" VARCHAR,
"runway_name" VARCHAR,
"aircraft_type" VARCHAR,
"aircraft_category" VARCHAR,
"airline" VARCHAR,
"other_port" VARCHAR,
"airport_code" VARCHAR,
"gate_penetration" DOUBLE,
"gate_name" VARCHAR,
"gate_penetration_time" VARCHAR,
"altitude" DOUBLE,
"center_deviation" DOUBLE,
"flight_no" VARCHAR,
"tail_number" VARCHAR,
"data_as_of" VARCHAR,
"data_loaded_at" VARCHAR
);Anyone who has the link will be able to view this.