Design and Construction of a Multi-Use Apron Facility for Code F Aircraft at Vancouver International Airport
Bibliographic record
Abstract
Vancouver International Airport (YVR) is Canada's second busiest airport, with some 15.5 million passengers and 274,400 aircraft movements in 2001. It is also the second largest international passenger gateway on the west coast of North America. It is a premier gateway to Asia and has been involved in an aggressive program of terminal and airside expansion since 1992. As part of its next major international terminal expansion, which will ultimately include six new Code F gates, YVR required a new remote apron which would act as an aircraft staging area to feed the terminal incorporating three deicing pads for Code E and Code F aircraft, remote cargo loading and refueling capabilities. The West Apron Expansion project combines 74,500m2 (802,000 S.F.) of rigid and flexible pavement structures, an extensive subsurface stormwater and deicing fluid collection system, low-visibility inset lighting for CAT III conditions and high-mast floodlighting to provide unobstructed parking and power-in/power-out maneuvering for Code E and F aircraft. This paper describes the West Apron Expansion project as an engineering and construction case study. The major pavement design elements included: geometry for Code F aircraft maneuvering; staged preloading of the site to induce long-term settlement on the weak (CBR 2) river delta deposits where YVR is founded; rigid pavement structures for the main parking and taxi lanes; rigid pavement panel sizes to suit gear tracks of the new large aircraft and adjustments for over 230 inset lights; grading and drainage plan suitable for apron parking and rapid removal of deicing fluids; and, flexible pavement structures with hot mix asphaltic concrete surfaces and cement-stabilized base courses for smaller remote aircraft loading. The main construction issues included multi-stage preloading to minimize imported subbase, seven construction stages to minimize operational impact on adjacent pavements, quality control management by the contractor and rigid pavement construction using fixed form paving without internal vibrators. The construction encompassed six main contracts completed over a two-year period ending in early 2002.
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.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".