Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Traffic Pattern Mitigation topic
No spam. Unsubscribe anytime.
Board proposes voluntary traffic‑pattern guidance to ease pattern saturation at Cleveland Airport
Summary
Members discussed voluntary procedures and outreach to flight schools after repeated pattern congestion; staff will consult FAA and TxDOT and draft language for stakeholders.
Get email alerts on the Traffic Pattern Mitigation topic
No spam. Unsubscribe anytime.
The Cleveland Airport Advisory Board discussed voluntary traffic‑pattern mitigation on Sept. 4 to address pattern saturation caused by training flights and multiple flight‑school operations.
Dean McFarland, chairman of the Cleveland Airport Advisory Board, opened discussion saying the airport is “a busy, uncontrolled airport” and that any measures absent a control tower must rely on voluntary compliance. Board members and pilots described times when multiple aircraft in the pattern made operations difficult for low‑time students and itinerant pilots.
Greg (board member and tenant) and other instructors supported a stakeholder‑led approach. Greg said the community needs “an informal, ground‑up kind of a solution” and recommended the board convene flight‑school operators to agree to voluntary procedures. Another member reported the board now has about eight months of monitoring data from the airport’s operations system; that dataset can show hours and days when the pattern is most congested.
Board members requested that staff consult the FAA and TxDOT Aviation to ensure any published guidance would comply with grant assurances and federal regulations. The chairman asked airport staff to draft suggested language, and members agreed to place the draft on a future agenda for possible issuance as a voluntary recommendation to flight schools and users.
The discussion emphasized that voluntary measures are non‑enforceable in the air: one board member noted that once an aircraft is airborne at an uncontrolled field the city has no authority over that aircraft’s operations. The board nevertheless endorsed outreach to local training providers, posting voluntary procedures in airport publications (e.g., AFD/EFB comments, AirNav), and circulating a letter to flight schools if TxDOT/FAA counsel finds no grant‑assurance conflict.
Next steps agreed: airport manager will contact FAA and TxDOT for compliance review, draft the recommended language, identify local flight‑school contacts, and return the matter to the board for a formal recommendation if appropriate.

