Laravel Aircrafts Laravel Package

Product Decisions This Supports

• Aviation/Travel Industry Use Cases: Enables rapid integration of IATA aircraft codes (and related metadata) for applications like flight booking, airline management, or travel analytics platforms.
• Data Consistency & Compliance: Reduces manual data entry errors and ensures adherence to IATA standards (ISO 3166-3, country codes) for aviation-related features.
• Build vs. Buy: Avoids reinventing the wheel for aircraft code lookups, saving dev time while maintaining flexibility for custom extensions (e.g., filtering by manufacturer, capacity, or range). v1.0.1 adds a migration-based install path (aircrafts:install --migrate), which means the reference data can live in our database and be refreshed or extended without forking the package — a meaningful de-risking of the "buy" side.
• Roadmap Prioritization: Critical for MVP development in aviation SaaS products (e.g., flight planning tools, airline APIs) or features requiring aircraft metadata (e.g., "Show flights by Boeing 737").
• Localization/Regulatory Features: Supports multi-country operations by tying aircraft data to ISO country codes, useful for global airlines or regulatory reporting.
• API/Integration Readiness: v1.0.1 fixes all-digit codes (e.g., 738) being returned as integers and makes AircraftCode accept integers, matching what JSON clients actually send. This directly unblocks public/internal API contracts and JS frontends — previously a silent data-integrity bug that would have surfaced as type mismatches in responses.

When to Consider This Package

• Avoid if:
  • Your app needs real-time aircraft data (e.g., live flight status, dynamic fleet updates)—this remains reference data, even when installed into the database.
  • You require commercial aircraft specs (e.g., engine details, passenger capacity) beyond IATA codes; consider APIs like OpenAirlines or FlightAware.
  • Your team lacks Laravel/PHP expertise, or you require a guaranteed support SLA / long-term vendor commitment.
  • You need historical aircraft data or deprecated models (this likely only includes active IATA codes).
• Consider if:
  • You’re building a Laravel-based aviation tool (e.g., internal airline portal, travel agency backend) where IATA codes are a core requirement.
  • You prioritize speed of development over customization—the package provides a ready-made dataset with minimal setup, now with a documented requirements section and a single install command.
  • Your use case aligns with reference data (e.g., dropdowns, validation, or metadata enrichment) rather than live queries — and sortBy mapping in v1.0.1 covers the common "sorted aircraft picker" pattern without custom query code.
  • You expose aircraft codes over an API or to a JS client — the v1.0.1 type guarantees (string codes out, integer input accepted) make this safe by default.

How to Pitch It (Stakeholders)

For Executives: "This Laravel package gives us a turnkey solution to integrate IATA aircraft codes—critical for [X aviation feature]—without hiring a data engineer. It’s a low-risk, MIT-licensed dependency that cuts dev time by weeks and ensures compliance with industry standards. The latest release also fixes a data-typing bug that would have caused integration friction with our API and frontend, and adds a database install path so we own and can refresh the data. The trade-off remains: it’s reference data, not live flight data — but for [use case], that’s a worthwhile exchange for speed and reliability."

For Engineering: *"Lightweight, Laravel-native access to IATA aircraft codes and country mappings. v1.0.1 is a maintenance release that closes two real footguns: codes() now always returns strings (previously all-digit codes like 738 came back as integers, which breaks strict comparisons and JSON contracts), and the AircraftCode value object now accepts an integer, so payloads from JSON clients validate without casting. It also documents requirements, an aircrafts:install --migrate path, and the sortBy mapping. Setup stays trivial: publish config, alias the provider, run the install command. Still ideal for:

• Validating user-input and API-supplied aircraft codes.
• Populating sorted dropdowns in admin panels (sortBy mapping).
• Enriching flight data with metadata (e.g., manufacturer, model). Caveats: no external API or real-time updates, and no formal support guarantee — pin the version, and use --migrate so we control data refreshes rather than waiting on upstream releases."*

For Design/Product: *"This package lets us drop in standardized aircraft names/codes (e.g., ‘B738’ for Boeing 737-800) anywhere in the app—no more manual lists or typos. Useful for:

• Flight search filters (‘Show only Airbus A320’), with built-in sorting so long aircraft lists stay usable.
• User profiles (‘Your frequent flyer status on A380’).
• Compliance features (e.g., ‘This aircraft operates in [ISO country codes]’). What changed: codes now always display consistently (no more numbers where letters-and-numbers were expected), and we can install the dataset into our own database—so updating it later is a data task, not an engineering project. Ask devs: can we extend this with custom fields (e.g., ‘preferred for long-haul’) via the published config?"*