First commit

.gitignore

@@ -0,0 +1,8 @@
+node_modules/
+dist/
+.parcel-cache/
+.env
+.DS_Store
+*.log
+.vscode/
+coverage/

.postcssrc

@@ -0,0 +1,5 @@
+{
+  "plugins": {
+    "@tailwindcss/postcss": {}
+  }
+}

.postcssrcZone.Identifier

@@ -0,0 +1,3 @@
+[ZoneTransfer]
+ZoneId=3
+HostUrl=https://drive.usercontent.google.com/download?id=1iGkHH39rEFOHEDjznbzXhyafayt5nyhG&export=download&authuser=0&confirm=t&uuid=fb85a7a6-76ac-48f7-8912-7c768145bc9a&at=AN8xHoq109b4hfEhXsocz57Dilfh%3A1758315864130

CUSTOM_FLIGHTPLAN_COMMANDS.md

@@ -0,0 +1,108 @@
+# Custom Flightplan Commands
+
+This system provides direct access to flightplan DTO objects with custom commands, allowing you to view and render flightplan data without relying on predefined hub commands.
+
+## Available Commands
+
+### Primary Command
+
+- **`FR <aircraft_id>`** - ERAM-style flight readout for specific aircraft
+  - Example: `FR UAL123`
+  - Shows formatted flight data like traditional ERAM systems
+  - Returns "REJECT - FLID NOT STORED" if aircraft not found
+  - Returns "REJECT - FLID DUPLICATION" with CID list if multiple matches
+
+### Basic Commands
+
+- **`FP <aircraft_id>`** - Display detailed flightplan for a specific aircraft
+  - Example: `FP UAL123`
+
+- **`FPHELP`** - Display help message with all available commands
+
+### List Commands
+
+- **`FPL [status]`** - List flightplans by status
+  - `FPL` or `FPL ALL` - Show all flightplans
+  - `FPL ACTIVE` - Show only active flightplans
+  - `FPL PROPOSED` - Show only proposed flightplans
+  - `FPL TENTATIVE` - Show only tentative flightplans
+
+### Search Commands
+
+- **`FPS [filters]`** - Search flightplans with multiple filters
+  - Filters: `status=<value>`, `dep=<airport>`, `dest=<airport>`, `alt=<altitude>`, `route=<waypoint>`, `acid=<aircraft_id>`
+  - Example: `FPS status=Active dep=KJFK`
+  - Example: `FPS dep=KJFK dest=KLAX`
+
+- **`FPF <criteria> <value>`** - Find flightplans by specific criteria
+  - Criteria: `DEP`, `DEST`, `WAYPOINT`, `ALT`, `TYPE`
+  - Example: `FPF DEP KJFK` - Find flights departing from JFK
+  - Example: `FPF WAYPOINT HOFFA` - Find flights routing via HOFFA waypoint
+  - Example: `FPF TYPE B738` - Find flights using Boeing 737-800
+
+### Statistics Command
+
+- **`FPSTATS`** - Display comprehensive flightplan statistics
+  - Shows total counts by status
+  - Top aircraft types
+  - Average speed
+  - Altitude distribution
+
+## Usage Examples
+
+```
+FR UAL123                    # ERAM-style flight readout for UAL123
+FP UAL123                    # Show detailed info for UAL123
+FPS dep=KJFK dest=KLAX      # Find all flights from JFK to LAX
+FPL ACTIVE                  # List all active flightplans
+FPF WAYPOINT HOFFA          # Find flights via HOFFA waypoint
+FPF DEP KORD                # Find all departures from Chicago O'Hare
+FPSTATS                     # Show statistics summary
+```
+
+## Features
+
+### Direct DTO Access
+- Access to complete `ApiFlightplan` objects
+- No dependency on hub-specific commands
+- Full control over data filtering and display
+
+### Rich Filtering
+- Filter by aircraft ID, departure, destination, altitude, status, route
+- Combine multiple filters in search commands
+- Case-insensitive searching
+
+### Multiple Display Modes
+- Table view for multiple flightplans
+- Detailed view for individual flightplans
+- Statistics view for data analysis
+
+### Real-time Updates
+- Automatically syncs with hub flightplan data
+- Redux state management for consistency
+- Command history tracking
+
+## Implementation Details
+
+### Files Created
+- `src/services/customFlightplanService.ts` - Core flightplan operations
+- `src/services/customFlightplanCommandParser.ts` - Command parsing logic
+- `src/hooks/useCustomFlightplanCommands.ts` - React hook for integration
+- `src/components/FlightplanVisualization.tsx` - UI components
+- `src/redux/slices/customFlightplanSlice.ts` - State management
+
+### Integration
+The system integrates seamlessly with your existing terminal interface in `App.tsx`. Commands are automatically detected and routed to the custom parser while preserving normal hub command functionality.
+
+### Data Sources
+- Pulls flightplan data from your existing `HubContext`
+- Works with the existing `Map<string, ApiFlightplan>` structure
+- Maintains compatibility with current hub operations
+
+## Status Display
+The terminal now shows:
+- Current flightplan count
+- Hub connection status
+- Reminder to use `FPHELP` for custom commands
+
+This gives you complete control over flightplan data visualization and manipulation while maintaining integration with your existing vFDIO system.