Skip to content

Web conference notes, 2024.01.18 (MDS Working Group)

Michael Schnuerle edited this page Feb 13, 2024 · 16 revisions

Web Conference

MDS Working Group

  • Monthly on Thursday at 9am PT, 12pm ET, 5/6pm CET

Conference Call Info

Zoom Registration Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4

One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York) - though we encourage Zoom

Agenda

Meeting Agenda

Advanced Air Mobility (AAM), Part 1

  • Intro and announcements (5 min)
  • Advanced Air Mobility
    • OMF Connection and MDS Status (10 min)
    • Eve Air Mobility (15 min)
    • Los Angeles DOT (10 min)
    • Orlando (10 min)
    • Questions and Next Steps

Urban/Advanced Air Mobility (UAM/AAM), Part 2: February 15, 2024

WGSC Meeting Organizers

  • Host: Pierre Bouffort, Blue Systems
  • Facilitator: Michael Schnuerle, OMF
  • Outreach: Andrew Glass Hastings, Michael Schnuerle, OMF
  • Note taker: Michael Schnuerle, OMF

Action Items and Decisions

  1. Review and share these meeting notes, slides, and recording with relevant people in your orbits.
  2. Review materials from LADOT, Urban Movement Labs, and former LADOT AAM fellow Clint Harper:
    1. Principles of the Urban Sky
    2. LADOT's UAM Policy Framework Considerations
  3. Attend next month's Advanced Air Mobility, Part 2 meeting February 15, 2024
    1. More discussion at this next meeting.
    2. Bring the right people from your organization and network to this public meeting.

Minutes

Notes

EVE Air Mobility

  • Key UAM Operating Environment
  • Air operations in cities will move more urban than usual and increase in tempo with more vehicles in the air
  • More flights with short turnaround times
  • Multiple vertiports for multiple operators
  • Limited ability to hover, so access to landing pad before landing is essential
  • Cities will have rules for data sharing needs and require this, like with MDS
  • Cities will demand benefits like equitability, and reduction in negative externalities
  • Integration into a multimodal system

Kinds of MDS data from UAM

  1. Origin
  2. Destination
  3. Aircraft properties
  4. ETA info
  5. Route
  6. Passenger Numbers
  7. Altitude
  8. GPS Coordinates
  9. Speeds

Additional data

  1. Vertiports landing pad, stands
  2. Electricity chargers, power

Balance of proprietary data with need to know and safety

ADS-B data every half a second: GPS, Altitude, Ground speed available day one

VFR (visual, less data) vs IFR (instrument, more data) flight rules

  • IFR includes owner, trip duration, vehicle identifiers

FAA UAM CONOPS v2.0 concept of operations data sharing concept

  • Thinking about corridors. Two way data exchange to PSU (Provider of services to UAM) to airport/operator/vertiports.

Cities may be tied into this PSU about where people can or can’t fly when

Urban Airtraffic managment system to streamline coordination across stakeholders

Fleet operators, vertiport automation, airspace, management with cities.

Eve has done pilots around a lot of this using some data around he world in many cities, mostly using helicopters

Value of UAM data to Govs

Transparency, Safety and Efficiency, Equity, Strategic Transportation Planning, Data Exchanges with users and emergency services

LADOT

MDS can help us with AAM as we work to see how we fit into the ecosystem

  • Collaboration is going to be key

7 principles of local policy making

  • Susatinability
  • Low noise
  • Local workforce development
  • Safety
  • Equity of access
  • Multimodal connectivity
  • Purpose driven dat sharing

Needs data to understand the connectivity of all the different modes, time in air, distance of trip, path. Wildfires, flight patterns

Urban Movement labs and Clint harper helped a lot with this

MDS integration and emergency communications are important to cities like LA

Orlando

  • Good when industry and cities and OMF are all speaking the same language
  • Looking at AAM for a few years now since a company announced plans for a vertiport in the city
  • About considering the positive and negative impacts, want to be proactive and ready
  • Cities know what’s best for cities
  • Regional look at this is important
  • Equity and jobs and access could be a benefit, concerned about noise and visual clutter
  • In Phase One, worked with NASA and community, planning.
  • It does not make sense economically for Orlando to build a vertiport - more pressing needs now, but there are economic benefits
  • Phase Two, police powers, zoning and regulation review
  • FDOT best practices: zoning ordinances is key - Have a vertiport approval process and rules for helicopters/heliports, but outdated 1960s guides and not meeting the needs of what AAM can with tempo and building guidelines
  • What data and what impacts will this have, even though zoning allows it many parts of the city
  • Orlando table top exercise, 4 scenarios, what works and doesn’t work

Questions like vertiport locations, safe operations, what type of info/data sharing will be required, who will stop the data and be responsible to update?

Resources listed from NASA, FDOT, American Planning Association guidebook, TRB, Conferences all over

Questions

  • Who do you need to bring in from your orgs to this conversation?
  • What operational data do cities believe they need?
  • What challenges and policies will cities need data to support?
  • What digital policy do cities need to publish for operators?
  • What do cities need to know and share with the public to allow this to ‘fly’ politically?
Clone this wiki locally