COMPANY RECORD · PHILADELPHIA, PA
Air Tight Heating And Cooling — permit history in Philadelphia, PA
Air Tight Heating And Cooling appears on 184 Philadelphia permit records from 2022 through 2026. Mechanical accounts for 99.5% of the record. This page describes recorded permits; it is not a live statement of availability, capacity or licensing.
What the permit record shows
In Philadelphia’s public permit data, Air Tight Heating And Cooling is primarily recorded for mechanical work. The record also contains 1 permits in other categories and 30 named participants on linked project timelines. That makes this page useful for checking past activity and preparing a conversation with the company. It does not tell us how much work the company has today, whether it is taking new jobs, or whether it is the right fit for a particular scope.
Work history
Permit categories
The table shows how the issuing authority classified permits that name Air Tight Heating And Cooling. These are permit counts, not revenue, crew size or market share. Small categories remain visible instead of being rounded away.
| Category | Permits | Share |
|---|---|---|
| Mechanical | 183 | 99.5% |
| Residential Building | 1 | 0.54% |
Activity by year
The record runs from 2022 to 2026. The yearly counts show when permits were issued. A busy year can contain several permits for one project, so the totals should be read as filing activity rather than a measure of current workload.
| Year | Permits issued |
|---|---|
| 2022 | 10 |
| 2023 | 23 |
| 2024 | 69 |
| 2025 | 58 |
| 2026 | 24 |
Names connected to the same projects
What a connection means
A connection means that Air Tight Heating And Cooling and another name appear on permits tied to the same resolved project timeline. It is a useful lead for research, but it is not proof of a partnership, a hiring relationship or a current contract. The source does not label every name as a company, so names are shown as published by the authority.
| Name in source | Linked permits | Last seen |
|---|---|---|
| Turn Key Realty Llc | 39 | 2026-05-13 |
| Center City Construction And Development Llc | 19 | 2025-10-11 |
| Andy Mulson | 13 | 2026-03-19 |
| Angel Oak Construction Llc | 13 | 2024-11-22 |
| Jerry Gialloreto | 8 | 2025-03-21 |
| Michael Loonstyn (Mjl Contracting Llc) | 8 | 2026-07-16 |
| Joseph M Loonstyn | 8 | 2025-12-15 |
| Zatos Construction | 6 | 2025-03-14 |
| Peroni Management Inc | 5 | 2026-05-13 |
| John Loonstyn | 4 | 2026-05-18 |
| Grosso Concrete Llc | 4 | 2025-09-26 |
| Bmc General Contracting Company Llc | 4 | 2026-05-08 |
How to use this page
For a contractor, supplier or project team
Use the record to build a shortlist and ask a more specific question. Start with the company’s dominant work category, check how recently it appears in the data, and compare any shared project names with the authority’s original record. If you are looking for current capacity, confirm the scope, schedule, license and insurance directly with the company.
What the history cannot answer
Permit history cannot confirm today’s backlog, prices, crew availability, licensing status, insurance or willingness to take a new job. A quiet period can also mean that work was filed outside this dataset. Historical evidence narrows the search; it does not replace qualification or a direct conversation.
Source and limits
Where the numbers come from
This page uses public Philadelphia L&I permit records available through 2026. Projects Ahead counts distinct permit numbers, groups the displayed trade names, and links records only when the available project fields support the connection. Names are kept as published; the public page does not add directory contacts or make a legal-entity claim.
Verify current details with the Philadelphia public permit source. The methodology explains the data treatment, and the page footer shows the source snapshot date.
Prepared by Projects Ahead from public municipal records. Figures describe historical filings and should be verified before a commercial decision.
Looking for the next opportunity?
A current project match requires a separate signal built from newer source activity and a verified project context. Permit history is the starting point, not a promise of the next job.