MétaCan
Menu
Back to cohort
Record W2509948169 · doi:10.1177/028072700202000306

Helping the other Victims <sup>1</sup> of September 11: Gander uses Multiple EOCs to Deal with 38 Diverted Flights

2002· article· en· W2509948169 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueInternational Journal of Mass Emergencies & Disasters · 2002
Typearticle
Languageen
FieldSocial Sciences
TopicInternational Law and Aviation
Canadian institutionsCarleton University
Fundersnot available
KeywordsGeographyBayNova scotiaMeteorologyAir traffic controlGovernment (linguistics)ArchaeologyCartography

Abstract

fetched live from OpenAlex

On September 11, 2001, after seeing three hijacked jets turned into missiles and a fourth crash in Pennsylvania, the United States ordered all U.S.- registered aircraft to land at the nearest airport and closed its airspace. When the decision was made, hundreds of commercial flights were over the Pacific or Atlantic en route to North America. Some had sufficient fuel to turn back. Most needed a North American airport to take them, and that airport had to be in Canada. The Canadian government, its air traffic control system, and Canadian airports were presented with a fait accompli. They had to accept hundreds of aircraft knowing - given what had happened - that one or more of them might be carrying terrorists or be under terrorist control. Worried about the possibility that some of these jets might attack major Canadian cities, the federal government ordered that they land at smaller communities along Canada's East Coast. On the East Coast, two factors affected precisely where those jets landed - the jet stream and the weather. The jet stream was far south that day, so most flights made their North American landfall at Newfoundland rather than Labrador. That took them to St. John's, Gander, or Stephenville, Newfoundland, rather than Goose Bay, Labrador. Then a light drizzle and fog hit Newfoundland's West Coast, dropping visibility to a mile at Stephenville. Aircraft heading there had to pull up and land in St. John's or Gander or continue to Halifax, Nova Scotia, or Moncton, New Brunswick. On Canada's West Coast, there was little choice: if the planes were going to land in Canada, for the most part they would have to land in Vancouver. As a result of all this, two Canadian cities - Halifax and Vancouver - received the most diverted flights on September 11. But when Gander's population - 10,347 - is considered, its intake was proportionally far greater. Gander took in 38 flights and 6,600 passengers, a 63 per cent increase in its population, compared to a two per cent increase in Halifax, less than a third of a one per cent increase for Vancouver. Even including nearby towns - Appleton, Gambo, Glenwood, Lewisporte, and Norris Arm - the Gander area's population is 18,882. That is still a 35 per cent increase. This article is about how Gander handled that situation. As will be shown, the community activated a number of emergency operations centres (EOCs) - and each ended up managing one aspect of the response. Though the airport was the key, the result was a coordinated system that ran smoothly without any single agency taking charge. This article describes how that system came about, why it worked, and how Gander avoided problems that often occur with multiple EOCs and emergent groups.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.851
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.029
GPT teacher head0.277
Teacher spread0.248 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it