T100 New Route Survival
Suitability and evaluation
Evaluation setting: retrospective research. Read the prediction setting and limitations below. Public validation is development data; downloadable holdout labels must stay outside the evaluated agent workspace.
When a U.S. certificated carrier starts scheduled passenger nonstop service on a domestic city market pair it has not served in the previous 12 months, will that service still be operating in the anniversary quarter 12-14 months later?
Population: Eligible unit is one carrier by directed origin city market by directed destination city market entry episode. In month M the carrier reports Class F scheduled passenger/cargo service, total Passengers greater than zero and total DepPerformed at least 8, and the same carrier performed zero departures on that directed pair in every month M-12 through M-1. Both endpoints are U.S. airports or territories in the U.S. carriers domestic T-100 table. The carrier is a U.S. certificated reporting carrier identified by UniqueCarrier. Months M+12 through M+14 must exist in the downloaded panel. Only entry months inside the frozen train eval and holdout windows are kept; no outcome condition enters eligibility. Rows lacking a fully reported anniversary window are omitted as unknown labels, never relabeled negative.
Target: label = 1 if the carrier's summed DepPerformed (departures performed) on the directed city-market pair over months M+12, M+13 and M+14 equals 0, i.e. the route is not operating at its one-year anniversary; label = 0 if any departures were performed in that three-month anniversary window.
Prediction time: Ninety days after the end of entry month M, after the monthly T-100 compilation for M is assumed available. Only T-100 records for months at or before M may enter features; months after M are unseen.
Splits: Frozen chronological boundaries by entry month, set before any modelling: train = entries in 2011-01..2014-06; eval (validation) = 2015-10..2016-09; holdout = 2018-01..2018-12. Two 15-month embargo gaps drop all entries in 2014-07..2015-09 and 2016-10..2017-12 so that no split's 14-month label window overlaps the next split's decision period. No entries after 2018-12 are used at all, because their anniversary windows fall inside the COVID-19 schedule collapse and would change the label's meaning. Data pulls cover 2010-01..2020-02 only.
Outcome horizon: 12 to 14 months after the entry month (three-month anniversary window).
Inputs: distance_miles: Reported nonstop segment distance between the two airports in statute miles; modal value across Class F entry-month rows; time-invariant proxy for block time, fuel burn and yield pressure.; entry_calendar_month: Calendar month of entry month M from 1 to 12; captures seasonality of route launches.; carrier_departures_prior_12m: Total DepPerformed by the carrier over months M-11 through M across all service classes reported in T-100; carrier scale and financial capacity proxy.; carrier_active_pairs_prior_12m: Number of distinct directed city-market pairs on which the carrier performed departures in months M-11 through M; network breadth.; carrier_route_attrition_prior_12m: Share of the carrier directed pairs that operated in month M-12 but had zero departures in month M; point-in-time rate at which this carrier abandons routes.; origin_market_departures_prior_12m: All-carrier, all-class departures performed at the origin city market over months M-11 through M; origin hub or station size.; dest_market_departures_prior_12m: All-carrier, all-class departures performed at the destination city market over months M-11 through M; destination size.; competing_carriers_prior_3m: Number of other UniqueCarrier codes with performed departures on the directed city-market pair in months M-3 through M-1; incumbent competition the entrant faces.; pair_departures_prior_3m: All-carrier, all-class departures performed on the directed city-market pair in months M-3 through M-1; zero indicates a previously unserved market rather than a contested one.; entry_month_departures: The carrier own Class F DepPerformed on the directed pair in month M; intensity of the initial schedule commitment.; entry_month_seats_per_departure: Class F Seats divided by Class F DepPerformed on the pair in month M; aircraft gauge committed to the route.; entry_month_load_factor: Class F Passengers divided by Class F Seats on the pair in month M; first-month demand realisation.; carrier_new_at_origin: 1 if the carrier performed zero departures at the origin city market in months M-12 through M-1, meaning the route also opens a new station; 0 if any departures occurred.; carrier_new_at_dest: 1 if the carrier performed zero departures at the destination city market in months M-12 through M-1; 0 if any departures occurred.