Mixed-use development near an airport influence zone

A mixed-use development team approached JSR when their planning consultant noticed that the proposed site fell within an airport influence area. The project included a podium, residential floors, rooftop services, and a future equipment zone, but the internal drawings did not yet describe the highest point in one consistent way. The architectural set used one reference, the structural notes used another, and the early application draft mentioned only the typical building height. This created a risk that the airport NOC file would be reviewed against incomplete or conflicting information.

JSR began by treating the file as a technical coordination exercise, not only as a form-filling task. The team reviewed the site location, plot boundary references, proposed building profile, rooftop projections, and available survey data. A fresh DGPS check was used to confirm coordinates and elevation references. Those values were then compared with the drawings, key plan, location map, and draft declarations so that every document spoke the same language. Where the project team had used different labels for terrace level, parapet, lift machine room, and rooftop services, JSR separated each item and identified the actual highest proposed point.

The next step was to prepare a cleaner submission package. The coordinate table, elevation note, proposed top elevation, ownership references, authorization papers, and drawing extracts were arranged in a sequence that made review easier. Instead of leaving the authority to interpret multiple height figures, the file clearly explained the base reference, ground elevation, structure height, and highest point considered for clearance. This also helped the client understand which future design changes could trigger a recheck before construction moved ahead.

The main benefit was reduced ambiguity. The project team avoided submitting a file that could have invited clarification on basic data consistency. Their consultants received a single coordinated reference set, and the management team had a clearer view of the approval dependency before freezing final height decisions. The case showed a common lesson in airport NOC work: delays often begin before submission, when drawings, survey values, and declarations are allowed to drift apart. A disciplined pre-check can turn the same information into a review-ready file.