Aircraft Development / Rank Picker has existed since 2016, but its public project history is not a complete changelog. The reliable current point is the live September 2, 2026 description naming A220-300. Older public pages and caches name other aircraft, while community documentation describes an earlier name and hangar layout. Those signals show change over time without proving every transition date or project outcome.
Dated project timeline
The gaps are meaningful. A project name may have changed between two visible snapshots, but the exact switch date cannot be narrowed to one day without archived creator text or an announcement. An older “current” label should be preserved as history rather than presented as a live fact.
Earlier place identity and layout
The dedicated community page says the experience was originally known as Pilot Training Plane Development. It describes a large hangar with black beams and ceiling windows, with an empty grass field outside. The current community description instead centers a grass baseplate, development assets, a football field, and an obby.
This is useful orientation for old screenshots. A hangar image may belong to an earlier version rather than a separate unofficial place. However, the community page does not provide a complete dated layout migration, so do not assign a year to the change unless a dated screenshot or creator post supplies one.
The same page mentions a Boeing 777 remodel and a temporary Airbus A340 covered in novelty decals during that work. This illustrates that not every airframe visible in the workspace was a normal current project or release candidate. Historical notes must describe the context, not simply extract an aircraft name.
Read former current-project labels carefully
Community pages and caches have surfaced Panavia Tornado, B-2 Spirit, and De Havilland Comet 4B as older current-project labels. They support a cautious “previously named” index, but cached results can be captured at different times, refreshed unevenly, or stripped of their original date.
Do not sort those projects only by the order in which a search engine displays them. Do not assume each was completed, cancelled, or released. A project can leave the current slot because it shipped, paused, moved, was replaced, or simply stopped being the focus; only a creator source can identify the outcome.
Use the Aircraft List to see each name and its evidence status without converting the candidates into an exhaustive release ledger.
Build a reliable comparison from visits
On each visit, record the live description, time, visible project sign, main model, and major environment landmarks. Use the same wide free-camera angle when possible. Then note installed sections separately from staged assets. This gives the next visit a reproducible baseline.
If the description changes, archive the old and new text with their observation times. That creates a bounded transition window: the change occurred after the last old observation and no later than the first new observation. It still does not prove when modeling began, ended, or moved into PTFS.
If the model changes without a description change, rejoin once and compare another server. Loading differences and server age can produce apparent history that is only a temporary mismatch.
What the Roblox updated timestamp means
Roblox’s game record reported 2026-09-01T21:42:58.0718748Z as the updated time during the September 2 check. That timestamp can change for many experience-level reasons. It does not explain which asset, description field, code, place, or setting changed.
Use the timestamp as a prompt to recheck the live description and scene. Do not turn it into “A220 modeling completed,” “new patch released,” or “next aircraft added” without a creator announcement or direct observation.
The Updates hub follows this rule by recording the exact public state and what remains unknown.
How to report a newly observed change
State the old observation date, new observation date, exact creator text, and what you directly saw. Use neutral language such as “the current-project label changed from X to Y between these checks.” Avoid announcing that X was cancelled or Y is nearly complete unless the creator says so.
Link to the official experience and preserve its numeric identity. If you cite a community page, label it community documentation and include the access date. If two sources disagree, use the live creator description for current status and keep the disagreement visible as a historical limitation.
Development history FAQ
What is the newest confirmed project?
A220-300, based on the live official description checked September 2, 2026.
What was developed before it?
Older public signals name Panavia Tornado, B-2 Spirit, De Havilland Comet 4B, and other community-documented work, but a complete sequence with dates is not available.
Does a former current project mean it released in PTFS?
No. Development focus and PTFS release are separate states. Verify release through current PTFS or creator-controlled sources.
Can the updated timestamp identify the change?
No. It tells you the experience record was updated, not which model or feature changed.
Why is the timeline incomplete?
The live description overwrites the previous current-project label, and community caches do not consistently preserve exact dates or outcomes.
How can I help myself compare future versions?
Keep dated screenshots from the same wide camera angle, save the exact live description, and distinguish installed parts from staged assets. Continue with A220-300 Development for the current observation checklist.