Can GenAnywhere adjust aircraft position and heading?
No. Aircraft are not scene objects, so position and heading are set in a design tool; the generated site supplies the apron and ground reference.
GenAnywhere cannot adjust aircraft position or heading, because no aircraft is in the scene to adjust. What the scene contains is the ground an aircraft would stand on: apron, taxiway, runway strips, terminal frontage and the buildings around them. Position and heading get set in a design tool or a stand-layout study, using the exported site as the reference frame.

1 The direct answer
1.1 Nothing in the scene to move
The edit controls act on buildings. A building can be replaced, moved, rotated, raised or lowered, and its type can be changed. Aircraft are equipment, so they are not in that set, and no part of the documented output covers them. If a review opens with a request to move an aircraft, the request belongs one step downstream, where the aircraft model exists and can be transformed. Saying this early is kinder than letting someone hunt for a handle that was never there. Put the sentence in the agenda, not in the middle of the discussion.

1.2 What the scene does hold
The scene holds the apron surface, the taxiway as ground, the terminal, the hangars and the land beyond the boundary. Those are generated from map and satellite data, with estimated heights and inferred types for the buildings. That content is what a stand-layout discussion actually needs, because the aircraft is placed relative to it. Ground, frontage and clear space set the constraints; the aircraft is the thing being tested inside them. The platform overview lists that content in more detail. If a building near the stand is wrong, correct it before the aircraft is added.
2 Where position and heading get set
2.1 Design tools and stand layout
Position and heading are set in the tool that owns the aircraft. That may be an airport design package, a stand-layout study, a simulation environment or a game engine used for visualisation. The aircraft model is transformed there, against the site that came out of the export. This split is ordinary in context work: the site is shared, and the equipment is managed by whoever is responsible for it. Two teams can then work on the same ground without overwriting each other's changes. Write the split into the project brief so new joiners learn it once.
2.2 Block models as stand-ins
Before a real aircraft model is available, a scaled block does most of the work. A box with the right wingspan and length, turned to a heading, shows whether the stand has room and whether the tail reaches past the stand edge. Label it as a block and give the dimensions in the caption. A block is easy to move and hard to mistake for a design, which makes it a good object for an early review with an audience that includes operations staff.
3 Using the site as a reference
3.1 Apron edges and terminal frontage
The apron edge and the terminal frontage are the two lines that most stand discussions refer to. Both are visible in the scene, and both can be corrected if the map got them wrong: a pier extension can be added as a building, a demolished shed removed. With those lines fixed, a heading drawn in another tool has something stable to relate to. Without them, every view is a different reference frame and no comparison holds. Where a pier has been extended since the imagery, add it as a building so the frontage matches the current drawing.
3.2 Reading a turning circle on the ground
A turning circle or a lead-in line can be drawn on the exported ground in the design tool, where it can be checked against the aircraft that will use it. The scene supplies the surface and the buildings around it; the design tool supplies the geometry and the check. Keeping the two apart means the circle can be revised without regenerating the site, and the site can be refreshed without losing the circle. That separation also makes the revision history easier to follow.

4 Limits
4.1 No clearance or wingtip check
The scene does not compute wingtip clearances, jet blast, pavement load ratings or obstacle limitation surfaces. Those need surveyed ground data, aircraft manuals and a qualified assessment. A view that shows an aircraft nose close to a pier is an illustration of the layout, not a finding about separation. Organisations such as the FAA publish the design guidance that belongs with those checks, and the review should point at it rather than at the picture. Keep the two documents separate so the illustration is not filed as an assessment.
4.2 No live traffic or schedule
Nothing in the model knows about arrivals, departures, towing movements or stand allocation. A still scene with one aircraft shows a geometry question, not an operation. If the review is about how a stand performs across a day, that belongs in a simulation or an operational study with real schedules. Use the scene to agree on the ground and the layout, then hand the operations question to the people who hold the data. If a simulation is planned, the site export can serve as its base surface.
5 A review that stays honest
5.1 Ground before aircraft
Show the ground before anything else. The opening view should be the airfield and its buildings, with no aircraft at all, so the audience understands what the model knows. Then bring in the block or the aircraft model and discuss placement. That order prevents the common failure where an audience assumes the aircraft came with the site and asks for changes the platform cannot make. It also makes the handover to the design tool feel like a natural next step. One slide of ground, one slide of placement, and the audience follows without a narration.
5.2 Labelling the stand-in
Label every aircraft that is not the real design. A caption that reads indicative position, wingspan and heading, not a design, removes most of the ambiguity in one line. Where a heading is being tested, say which heading and why. Labels cost little and they stop a screenshot from being reused as evidence of an arrangement nobody approved. That risk grows with the quality of the visual, which is worth remembering before a polished image leaves the room. Keep the original block screenshot too, so the difference between placeholder and proposal stays visible.
6 After the review: export and handover
6.1 Export and import
Export a GLB when the layout work moves to another team. The file carries terrain, buildings and vegetation, and it opens in 3D, BIM, GIS and game engine workflows where aircraft can be added. Test the import before a meeting depends on it, because scale and axis conventions vary between applications. A file that arrives at the wrong scale wastes a session and undermines trust in every later export. Keep the export and the receiving tool's import log together, so a scale question can be traced later.
6.2 Coordinate agreement
Agree on a coordinate reference and a unit before the site is exported, and write both into the handover note. A scene in metres and a design in feet will produce an aircraft that looks wrong for reasons nobody can see on screen. If the receiving tool expects a specific origin, place the site so the origin lands somewhere the team recognises, such as a terminal corner or a stand centre. Write the choice down, because the next export will need the same origin.
6.3 Who owns the aircraft file
Say who owns the aircraft asset and who updates it. In most projects that is the design team, sometimes the operator, occasionally a simulation group. Naming the owner prevents a stale model from being reused after a fleet change. It also settles the question of which version was shown in a review, which comes up sooner or later in any project that runs for more than a few months. An owner and a version number turn that question into a lookup.
Open the GenAnywhere app and frame an apron layout
7 FAQ
FAQ-1 Can I move an aircraft in GenAnywhere?
No, because no aircraft is generated. The editable objects are buildings plus the terrain, buildings and vegetation layers. Aircraft position and heading are set in a design or visualisation tool after the site is exported. That split keeps the site stable while the aircraft is revised, which is what a stand-layout study needs. Bring the aircraft in downstream and label it clearly, so nobody asks the scene to do something it was not built for.
FAQ-2 Can I test a heading in the scene?
You can place a block or a model in the downstream tool and turn it to a heading against the exported ground. The scene will show how it sits relative to the apron and the terminal, and it will not check separation, blast or pavement loading. That is a useful split: the arrangement is visual, the checks are analytical. Report the heading you tested so the next session can repeat the view.
FAQ-3 Does the export include aircraft?
No. The GLB carries the site: terrain, buildings, vegetation and any edits you made. Aircraft, ground vehicles and jet bridges stay outside. The receiving team adds them in its own environment, using its own assets. Note this in the handover, especially when the audience has seen a review image with aircraft in it, because the picture and the file will not match. Say which image was which before someone compares them.
FAQ-4 What is the scene good for at an airport?
Orientation and layout. It shows where the apron sits, how the terminal frontage runs, which buildings frame the stand and how the ground falls. That answers most opening questions in a stand or apron review. It is not a substitute for airfield drawings or operational data, and the review should keep those beside the model rather than behind it. Treat the scene as the map on the wall, not the report on the table.
See how an airport site moves into a GLB workflow
Content and technical notes
This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.
Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.
For technical questions or corrections, contact support@genanywhere.com.
Last reviewed: 2026-11-13.