Actions44
- Contact Actions
- Aircraft Actions
- Get
- Get List
- Get by Registration
- Get Identification
- Get Status
- Get Maintenance
- Get Flights
- Get APU
- Get Avionics
- Get Engine
- Get Airframe
- Get Additional Equipment
- Get Features
- Get Interior
- Get Exterior
- Get Leases
- Get Company Relationships
- Get Pictures
- Get Bulk Aircraft Export Paged
- Get Condensed Owner Operators Paged
- Get Event List Paged
- Get History List Paged
- Company Actions
- Market Actions
Overview
This node integrates with the JetNet API to retrieve detailed aviation industry data related to aircraft. Specifically, the "Get Flights" operation under the "Aircraft" resource fetches the flight history of a specified aircraft by its unique ID.
Use cases include:
- Tracking historical flight activity for an aircraft.
- Analyzing usage patterns or operational history.
- Integrating flight data into aviation management or analytics workflows.
For example, an operator could use this node to automatically pull recent flight logs for a particular aircraft to monitor utilization or maintenance scheduling.
Properties
| Name | Meaning |
|---|---|
| Aircraft ID | The unique identifier of the aircraft whose flight history you want to retrieve. |
Output
The output is JSON data representing the flight history of the specified aircraft. This typically includes details such as flight dates, routes, durations, and other relevant flight information as provided by the JetNet API.
The node returns an array of flight records if multiple flights exist. Each item in the output corresponds to one flight entry.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the JetNet API service.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is
https://customer.jetnetconnect.com.
Troubleshooting
- Invalid Aircraft ID: If the aircraft ID is incorrect or does not exist, the API may return an error or empty results. Verify the aircraft ID before running the node.
- Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Connectivity problems to the JetNet API endpoint will cause request failures.
- API Rate Limits: Excessive requests might be throttled; consider adding delays or handling rate limit errors gracefully.
- Empty Results: If no flight history exists for the given aircraft, the output may be empty or minimal.
Links and References
- JetNet Official Website
- JetNet API documentation (not publicly linked here; refer to your JetNet account resources)