A tool by Firecrawl · uses 6 tools · Travel

Charter aircraft vetting for a jet broker

Use when a private jet charter broker is vetting the specific aircraft an operator offers for a client trip. Confirms the tail number's registered owner and recorded liens in the FAA registry, lists airworthiness directives for the make and model, and checks delay programmes at the departure and arrival airports on the day. Produces a vetting note to file with the booking.

Open in ChatGPT Open in Claude

Save a copy for your team

Tools it calls

Each tool's price and track record across every agent today. Empty means the call worked and found nothing.

ToolPriceMedianSuccessEmpty

FAA public recordsAircraftPrice5 creditsMedian–Success–Empty–
FAA public recordsAircraft searchPrice5 creditsMedian–Success–Empty–
FAA public recordsAircraft documentsPrice5 creditsMedian–Success–Empty–
FAA public recordsAirworthiness directive searchPrice5 creditsMedian414 msSuccess98.5%Empty0%
FAA public recordsAirport delaysPrice5 creditsMedian–Success–Empty–
National Weather Service API (api.weather.gov)Alerts activePrice5 creditsMedian558 msSuccess100%Empty0%

Instructions

What your agent follows when it runs this tool. Paste them into any assistant connected to Firecrawl.

# Charter aircraft vetting for a jet broker

For the operator name, the tail number offered and the departure and arrival airports.

## 1. Who owns the aircraft

1. Read @[FAA · Aircraft](alexandria:faa-gov/aviation-records/aircraft) for the tail number: registered owner, make, model, year, registration status and expiry.
2. List the operator's fleet with @[FAA · Aircraft search](alexandria:faa-gov/aviation-records/aircraft_search) (`owner_name`). A tail registered to an unrelated owner deserves a question about the operating arrangement.
3. Read @[FAA · Aircraft documents](alexandria:faa-gov/aviation-records/aircraft_documents) for recorded liens or security agreements.

## 2. Model safety notices

4. Search @[FAA · Airworthiness directive search](alexandria:faa-gov/aviation-records/airworthiness_directive_search) for the make and model with `status` current. Keep the directives and their subjects.

## 3. Trip day

5. Check @[FAA · Airport delays](alexandria:faa-gov/aviation-records/airport_delays) for both airports on the day, and @[National Weather Service · Alerts active](alexandria:api-weather-gov/weather/alerts_active) around them.

## Write the vetting note

- **Aircraft:** tail, make, model, year, owner of record, registration status and expiry, recorded documents.
- **Notices:** current directives for the type (compliance itself cannot be confirmed from public data).
- **Trip day:** delay programmes and weather alerts.
- **Questions for the operator:** three, each tied to a finding.
- **Sources:** cite each fact to its capability and date. Operator certificates and safety audits are not covered; say so.

All Firecrawl tools