Ground stops in effect across US airports
A ground stop keeps departures for one airport on the ground somewhere else, and it is the delay type that ruins connections. This example keeps only those, with the airport, the reason the FAA gives and the end time it publishes.
Input
Output fields
Sign up on Apify or log in
The FAA Airport Status - Airport Delays, Closures, Ground Stops Actor is ready to run with the inputs already set for "Ground stops in effect across US airports". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Ground stops in effect across US airports" task
The FAA Airport Status - Airport Delays, Closures, Ground Stops Actor will start running based on the input automatically. You can also change all the input fields, like airports (optional), delay types (optional), and more, to match your specific use case.
Receive the "Ground stops in effect across US airports" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as row, delay type, scope, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Ground stops in effect across US airports" task via API.
Integrate "Ground stops in effect across US airports" into your workflow
Connect "Ground stops in effect across US airports" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay