{"_meta":{"attribution":"Data aggregated by pdata.world (https://pdata.world) from 8 prediction-market venues; CC BY 4.0; source data © each venue.","canonical_url":"https://pdata.world/events/kalshi/KXGROUNDSTOPCAUSE-26DEC01","as_of":"2026-11-14T00:57:16.252497Z","docs":"https://api.pdata.world/docs","cite_as":"According to pdata.world (tracking Kalshi): \"What caused the FAA's nationwide ground stop?\" — 13 markets; highest \"Specific cause confirmed\" at 95% as of 2026-11-14 UTC. https://pdata.world/events/kalshi/KXGROUNDSTOPCAUSE-26DEC01","source_url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01"},"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01","ticker":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01","title":"What caused the FAA's nationwide ground stop?","description":null,"image":null,"icon":null,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":null,"volume":317417.8,"volume_24hr":303902.66,"volume_24h_change":null,"normalized_vol_24hr":46.4704475402832,"normalized_volume":41.77091979980469,"liquidity":null,"open_interest":141355.29,"categories":["Politics"],"tags":[],"synthetic":false,"is_group":false,"group_key":null,"parent_event_id":null,"probability":null,"spread":null,"top_outcome":"Specific cause confirmed","top_outcome_probability":0.95,"top_outcome_prob_24h_change":0.93,"top_outcome_volume_24h_change":28649.72,"updated_at":"2026-11-14T00:57:06.662119Z","fetched_at":"2026-11-14T00:57:06.662119Z","added_at":"2026-11-13T21:39:10.299401Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","chart_24h":[150.93,26120.66,90710.29000000001,179396.32,274531.77999999997],"kind":"live","mutually_exclusive":false,"markets_total":13,"markets":[{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-ANYC","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-ANYC","question":"Will it be confirmed that a specific identified malfunction, error, damage or other event caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Specific cause confirmed","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a specific identified malfunction, error, damage or other event caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.95,0.050000000000000044],"probability":0.95,"spread":0.010000000000000009,"active":true,"closed":false,"start_date":"2026-11-13T22:37:11Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":29110.32,"volume_24hr":28814.55,"prob_24h_change":0.93,"volume_24h_change":28649.72,"normalized_vol_24hr":35.471534729003906,"normalized_volume":29.56429672241211,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T22:29:58.660940Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.97,0.95,0.93]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-SOFT","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-SOFT","question":"Will it be confirmed that a software or configuration error caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Software/config error","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a software or configuration error caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.84,0.16000000000000003],"probability":0.84,"spread":0.05999999999999994,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":22699.8,"volume_24hr":22693.91,"prob_24h_change":-0.20999999999999996,"volume_24h_change":22589.13,"normalized_vol_24hr":33.877437591552734,"normalized_volume":28.224061965942383,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.99,0.78,0.71,0.72,0.8]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-FAIL","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-FAIL","question":"Will it be confirmed that an equipment, software, power or telecommunications failure caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"System failure","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that an equipment, software, power or telecommunications failure caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.77,0.22999999999999998],"probability":0.77,"spread":0.039999999999999925,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":31984.0,"volume_24hr":31978.59,"prob_24h_change":-0.19999999999999996,"volume_24h_change":31267.69,"normalized_vol_24hr":36.089935302734375,"normalized_volume":30.067598342895508,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.99,0.72,0.8,0.82,0.72]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-VEND","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-VEND","question":"Will it be confirmed that a failure at a telecommunications carrier or other FAA contractor caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Contractor failure","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a failure at a telecommunications carrier or other FAA contractor caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.76,0.24],"probability":0.76,"spread":0.030000000000000027,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":39521.08,"volume_24hr":37944.23,"prob_24h_change":0.9,"volume_24h_change":37292.94,"normalized_vol_24hr":37.31745529174805,"normalized_volume":31.09971046447754,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.34,0.33,0.41,0.86]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-LHX","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-LHX","question":"Will it be confirmed that a failure in a network or system run by L3Harris caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"L3Harris","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a failure in a network or system run by L3Harris caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.72,0.28],"probability":0.72,"spread":0.030000000000000027,"active":true,"closed":false,"start_date":"2026-11-13T23:32:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":30821.28,"volume_24hr":29715.28,"prob_24h_change":0.61,"volume_24h_change":28594.15,"normalized_vol_24hr":35.45811462402344,"normalized_volume":29.69867515563965,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T23:37:14.776614Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.16,0.86]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-UPGR","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-UPGR","question":"Will it be confirmed that maintenance, an upgrade or another planned change to an FAA or contractor system caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Maintenance/upgrade","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that maintenance, an upgrade or another planned change to an FAA or contractor system caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.68,0.31999999999999995],"probability":0.68,"spread":0.039999999999999925,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":37031.17,"volume_24hr":33582.81,"prob_24h_change":0.72,"volume_24h_change":31078.67,"normalized_vol_24hr":36.03627395629883,"normalized_volume":30.029327392578125,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.05,0.14,0.16,0.63]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-HUMN","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-HUMN","question":"Will it be confirmed that human error caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Human error","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that human error caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.14,0.86],"probability":0.14,"spread":0.03,"active":true,"closed":false,"start_date":"2026-11-13T22:36:25Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":18731.74,"volume_24hr":18288.74,"prob_24h_change":0.12,"volume_24h_change":17979.19,"normalized_vol_24hr":32.32402420043945,"normalized_volume":26.96076011657715,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T22:29:58.660940Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.41,0.16,0.17]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-SMRT","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-SMRT","question":"Will it be confirmed that a problem with the FAA's SMART air traffic management system caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"SMART system","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a problem with the FAA's SMART air traffic management system caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.1,0.9],"probability":0.1,"spread":0.009999999999999995,"active":true,"closed":false,"start_date":"2026-11-13T22:19:50Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":47311.96,"volume_24hr":47150.11,"prob_24h_change":-0.15999999999999998,"volume_24h_change":43922.11,"normalized_vol_24hr":38.48648452758789,"normalized_volume":32.29975509643555,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T22:13:31.544562Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.24,0.08,0.26,0.08]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-AIER","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-AIER","question":"Will it be confirmed that an error by an AI system or AI agent caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"AI system error","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that an error by an AI system or AI agent caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.09,0.91],"probability":0.09,"spread":0.04999999999999999,"active":true,"closed":false,"start_date":"2026-11-13T22:36:49Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":37564.85,"volume_24hr":32274.61,"prob_24h_change":0.03,"volume_24h_change":25520.8,"normalized_vol_24hr":34.676631927490234,"normalized_volume":29.69716453552246,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T22:29:58.660940Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.13,0.15,0.14]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-VZ","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-VZ","question":"Will it be confirmed that a failure in a network or system run by Verizon caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Verizon","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a failure in a network or system run by Verizon caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.07,0.9299999999999999],"probability":0.07,"spread":0.049999999999999996,"active":true,"closed":false,"start_date":"2026-11-13T23:32:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":3536.14,"volume_24hr":3536.14,"prob_24h_change":0.07,"volume_24h_change":3536.14,"normalized_vol_24hr":22.485118865966797,"normalized_volume":18.732032775878906,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T23:37:14.776614Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.08]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-DMGE","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-DMGE","question":"Will it be confirmed that accidental damage to a cable, line or other physical equipment caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Physical damage","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that accidental damage to a cable, line or other physical equipment caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nSystem failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance/upgrade: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nPhysical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware/config error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nContractor failure: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\nSMART system: a malfunction or error in, or the deployment or rollout of, the FAA's SMART air traffic management system, including its interaction with other FAA systems\nHuman error: a mistake by a person, such as an FAA employee, air traffic controller, technician or contractor, set off the outage, including a wrong command, setting, procedure or physical action. A deliberate act meant to disrupt equipment or operations does not count.\nAI system error: an AI system or AI agent (a machine-learning model, large language model or autonomous agent) itself produced the action, output or change that caused the outage, and the Source Agency describes that system as AI. It does not count if AI was only part of the affected system, used by staff or contractors, running at the time, or used to help write software that later failed.\nSpecific cause confirmed: a Source Agency confirms what caused the telecommunications outage behind the ground stop by naming a particular malfunction, error, damage or other event. If no cause is confirmed before Dec 1, 2026, this market resolves to No.\nL3Harris: the failure, damage, error or work behind the outage was in equipment, a network or a system that L3Harris Technologies runs, manages or oversees for the FAA, whoever caused it\nVerizon: the failure, damage, error or work behind the outage was in equipment, a network or a system that Verizon runs, manages or oversees for the FAA, whoever caused it\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop\n\nThis market is NOT mutually exclusive: more than one market can resolve to Yes. For example, a problem with the SMART rollout can also count for Maintenance/upgrade and, if it is a software or configuration fault, for Software/config error.","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.05,0.95],"probability":0.05,"spread":0.010000000000000002,"active":true,"closed":false,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":19105.46,"volume_24hr":17923.69,"prob_24h_change":0.04,"volume_24h_change":17760.44,"normalized_vol_24hr":32.24330139160156,"normalized_volume":26.90456199645996,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-14T00:57:06.941032Z","fetched_at":"2026-11-14T00:57:06.941032Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":[0.0,0.07,0.06,0.07,0.06]},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-CYBR","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-CYBR","question":"Will it be confirmed that a cyberattack caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Cyberattack","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that a cyberattack caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nEquipment or system failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance or upgrade work: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nCable cut or physical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware or configuration error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nTelecom carrier or contractor fault: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.0,1.0],"probability":0.0,"spread":0.99,"active":false,"closed":true,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":0.0,"volume_24hr":0.0,"prob_24h_change":0.0,"volume_24h_change":0.0,"normalized_vol_24hr":null,"normalized_volume":null,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-13T21:56:26.922271Z","fetched_at":"2026-11-13T21:56:26.922271Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":null},{"source":"kalshi","id":"KXGROUNDSTOPCAUSE-26DEC01-SABO","event_id":"KXGROUNDSTOPCAUSE-26DEC01","slug":"KXGROUNDSTOPCAUSE-26DEC01-SABO","question":"Will it be confirmed that intentional radio interference, jamming or physical sabotage caused the FAA's nationwide ground stop on Nov 13?","group_item_title":"Jamming or sabotage","description":"If a Source Agency confirms after Issuance and before Dec 1, 2026 that intentional radio interference, jamming or physical sabotage caused the FAA's nationwide ground stop on Nov 13, then the market resolves to Yes.\n\n---\n\nThis must be confirmed, verified, or established as factual by at least one Source Agency.\n\nThe ground stop is the nationwide departure ground stop the FAA ordered on Nov 13, 2026. A cause counts if a Source Agency reports it as a cause of the ground stop or of the radio, radar or other system outage behind it. More than one market can resolve to Yes.\n\nEquipment or system failure: a malfunction of hardware, software, power or telecommunications equipment used by the FAA or its contractors, including one set off by maintenance work or accidental damage. A cyberattack, jamming or sabotage is not a failure.\nMaintenance or upgrade work: planned maintenance, an upgrade, a configuration change or a cutover on an FAA or contractor system\nCable cut or physical damage: accidental damage to a cable, line, antenna or other physical equipment, including by construction work or weather\nSoftware or configuration error: a fault in software, or a wrong setting or configuration, in an FAA or contractor system, including one introduced by an update or upgrade\nTelecom carrier or contractor fault: the failure, damage, error or work behind the outage was in equipment, a network or a system run by a company other than the FAA, such as a telecommunications carrier or an FAA contractor\n\nThe following do NOT count:\nA report that a cause is suspected, being investigated or has not been ruled out\nA statement that the ground stop followed a communication, radio or radar outage or issue, without saying what caused that outage\nA cause of a different outage or ground stop","image":null,"icon":null,"outcomes":["Yes","No"],"outcome_prices":[0.0,1.0],"probability":0.0,"spread":0.99,"active":false,"closed":true,"start_date":"2026-11-13T21:37:00Z","end_date":"2026-12-08T15:00:00Z","closed_time":"2026-12-01T04:59:00Z","result":null,"volume":0.0,"volume_24hr":0.0,"prob_24h_change":0.0,"volume_24h_change":0.0,"normalized_vol_24hr":null,"normalized_volume":null,"liquidity":null,"categories":["Politics"],"countries":[],"updated_at":"2026-11-13T21:56:26.922271Z","fetched_at":"2026-11-13T21:56:26.922271Z","added_at":"2026-11-13T21:39:10.501829Z","url":"https://kalshi.com/markets/kxgroundstopcause/what-caused-the-faas-nationwide-ground-stop/kxgroundstopcause-26dec01","event_title":"What caused the FAA's nationwide ground stop?","chart_24h":null}]}