The accurate Bumpy Flight aircraft list is the list shown by the current game, not a frozen count copied from an undated page. The official experience description confirms that players can unlock multiple aircraft. It does not publish a complete permanent catalog, and the experience is labeled beta. This page gives you a repeatable way to review every visible plane without inventing names, requirements, or statistics.
Catalog rule: record the exact in-game name, lock state, displayed requirement, item type, and date checked. If one field is missing, label it unknown instead of filling it from memory.
Open the current aircraft selector
Join the official Roblox experience at Place 87046419551816 and enter the aircraft selection or preparation flow presented by the game. Interface labels can move between updates, so follow the current button rather than an old screenshot. Confirm you are viewing aircraft and not a cosmetics-only panel.
Scroll through the entire visible selection once before making a purchase. Note whether entries are available, locked, preview-only, or equipped. A locked thumbnail is still evidence that an entry is shown, but not evidence that it is currently obtainable by your account.
If the interface groups models and skins together, inspect the detail text for each entry. A paint or cosmetic for a base plane should not be counted as a separate flyable aircraft.
Record each entry consistently
Use five columns in a private note: displayed aircraft name, availability, requirement, compatible cosmetic information, and checked date. Add a sixth observation column only after a test flight. Preserve capitalization and punctuation because similar names can refer to different items.
For a locked entry, copy the exact requirement shown. It might refer to progression, currency, a purchase, or another condition. Do not assume all aircraft use the same unlock path. For an available entry, verify whether “select,” “equip,” or another action changes the active aircraft.
The date matters because beta catalogs are fluid. A record checked on August 30, 2026 describes that version; it is not a promise that every later server will match.
Separate facts from community data
Community aircraft databases can reveal names worth checking, but treat them as leads. Verify each name against the live selector. If a community page gives an exact price or level, compare it with the current requirement. Keep the current in-game value and annotate the discrepancy rather than blending the two.
A search result snippet is especially weak evidence because it may be truncated, stale, or about a different Roblox experience with a similar title. Confirm the Place ID and game name before using any list.
The official description is strong evidence for the existence of aircraft unlocks and cosmetics. It is not evidence for a specific model count, tier order, or hidden performance statistic.
Test whether an entry is a flyable aircraft
Select or equip the item, begin a normal preparation sequence, and observe what spawns. Check that the exterior and interior match the selected entry. Complete the ordinary luggage, fuel, and passenger objectives shown by the game. Then take a controlled flight using small inputs.
If only colors or decals change while the base layout remains the same, the entry may be a skin. If a distinct aircraft appears, record it as a flyable model. Do not use visual size alone; some cosmetics can make a familiar plane look different.
When the selection does not apply, re-open the interface and verify the equipped state. A preview is not the same as ownership or activation.
Compare aircraft without fake stats
Public first-party material reviewed does not expose a numeric speed, handling, passenger capacity, durability, or fuel-efficiency table. You can still compare observations, but describe the test. “Needed fewer correction taps on two similar approaches” is more honest than assigning a made-up handling score.
Use the same controller or keyboard setup, similar crew size, and similar route cues. The official keyboard inputs are W/S for pitch, A/D for turning, Shift for more throttle, and Ctrl for less. Use short taps so your own overcorrection does not dominate the comparison.
Interior layout is also relevant. Walk from the cockpit to passenger seats, supply areas, cargo space, and repair points. Record whether routes were clear for your crew, while acknowledging that beta layouts can change.
Handle hidden, limited, or unavailable entries
If an aircraft appears in an image but not in the current selector, label it “not verified in current catalog.” It could be future content, removed content, a limited reward, a development image, or simply a cosmetic. Do not publish an unlock instruction without a live requirement.
If the selector shows a limited or event condition, copy the exact text and date. Do not assume the event returns. If an entry has no visible method, state that the current unlock method is not shown.
Refresh your list after updates
The official title included an update marker at the research check, and the experience was actively updated. After a patch, inspect the first entry, last entry, and every previously locked target. Confirm names, order, requirements, and equipped state. Re-run one flight before claiming that handling changed.
Maintain change notes instead of silently overwriting your observations. This distinguishes a real update from a previous transcription mistake.
Common list errors
- Counting skins as aircraft.
- Copying an exact model total without a current selector check.
- Mixing entries from a similarly named game.
- Treating preview access as ownership.
- Publishing community prices as first-party facts.
- Calling subjective handling a hidden numeric stat.
- Omitting the date and beta version scope.
Once you identify a target, use Unlock Aircraft to plan progression and Skins and Cosmetics to verify customization separately.