> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pilotflows.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome

> Understand what PilotFlows is, who it is for, and how the platform fits together

## What is PilotFlows?

PilotFlows is a connected platform for aviation and skydiving. You can use it to log flights or jumps, manage aircraft, run a flight school, or handle dropzone operations without jumping between separate tools.

Instead of treating logbooks, scheduling, maintenance, training, and operations as separate systems, PilotFlows keeps them in one place so the data stays connected.

## What you can do with it

<CardGroup cols={3}>
  <Card icon="book" title="Pilot Logbook">
    Log flights, track currency, review analytics, and keep records that support EASA and FAA workflows.
  </Card>

  <Card icon="parachute" title="Skydiving Logbook">
    Record jumps, follow progression, manage gear details, and review canopy and freefall stats.
  </Card>

  <Card icon="plane" title="Aircraft Management">
    Schedule aircraft, manage tech logs, track maintenance, and keep documents and status in one place.
  </Card>

  <Card icon="graduation-cap" title="Flight School">
    Organize students, training programs, endorsements, and electronic training records.
  </Card>

  <Card icon="users" title="Skydiving Operations">
    Run manifesting, load planning, training flows, and day-to-day dropzone operations with built-in safety checks.
  </Card>

  <Card icon="chart-bar" title="Shared Platform Tools">
    Use scheduling, compliance tracking, analytics, team management, and other shared features across products.
  </Card>
</CardGroup>

## Who PilotFlows is for

PilotFlows works for both individuals and organizations:

* **Pilots and skydivers** who want a modern digital logbook with better structure, visibility, and reminders.
* **Aircraft owners, clubs, and operators** who need scheduling, maintenance tracking, and operational oversight.
* **Flight schools and instructors** who want digital training records and a clearer view of student progress.
* **Dropzones and skydiving teams** who need manifesting, checkouts, planning, and safer day-to-day coordination.

## Why the platform feels different

Each part of PilotFlows can stand on its own, but the real value comes from how the pieces connect.

<Steps>
  <Step title="Your records stay connected">
    A pilot's logbook, a student's training history, and an aircraft's schedule do not live in separate silos. That makes it easier to understand what happened, what is due, and what needs attention next.
  </Step>

  <Step title="Operations become easier to manage">
    Scheduling, maintenance, training, compliance, and reporting all draw from the same source of truth. You spend less time duplicating data and less time checking for mistakes.
  </Step>

  <Step title="You can grow without changing systems">
    You might start with a personal logbook and later need organization features, or begin with an operational need and expand from there. PilotFlows is built to support that path.
  </Step>
</Steps>

<Info>
  PilotFlows is designed for real-world aviation and skydiving workflows, with support for compliance, auditability, and operational clarity rather than just simple record keeping.
</Info>

## Where to go next

<CardGroup cols={2}>
  <Card icon="lightbulb" href="/getting-started/concept" title="Understand the Concept">
    Learn how personal and organization experiences are structured inside PilotFlows.
  </Card>

  <Card icon="rocket" href="/getting-started/quickstart" title="Open the Quickstart">
    Move on to the setup flow when you are ready to start using the platform.
  </Card>

  <Card icon="question-mark-circle" href="/support/faq" title="Read the FAQ">
    Check common questions if you want quick answers before diving deeper.
  </Card>

  <Card icon="chat-bubble-left" href="/support/contact" title="Contact Support">
    Reach out if you are unsure where to start or need help with a specific use case.
  </Card>
</CardGroup>