• No labels

2 Comments

  1. David Allbee

    May 02, 2026

    02MAY2026
    Tech – D. Allbee

    Taxi – 1603
    Takeoff – 1610
    Landed – 2033


    Nimbus did not initialize properly at first (flashed, then disappeared). Second time it came up fine.
    Mousepad on keyboard acting flaky. All other kybd functions OK.


    1647 – power cycled VCSEL. Reporting a few variables including SMPLSRINT_VXL, but isn’t displaying any dew point. Same conditions after power cycle.


    Cameras in-op today. Janine says she sees Left Camera on the ground, but no others. There are no images being displayed in flight.


    Performed a CV leak drill. Vented the cabin. Deployed oxygen masks. Etc.


    Systems checked out, good:
    2D-S, CDP, DPL*, DPR*, CAVPs, RTH1/2, RTF, NOSETEMP, TCAB, PCAB, Winds, PDumps, PLWC**, RICE**, Hexchat, catalog maps, GPS, IRS, SATCOM, CV

    * DPL and DPR do not operate well at high altitudes.
    ** Did not encounter any liquid water to properly test PLWC and RICE, but housekeeping looks good.


    Systems that need attention:
    ADS keyboard – may need to swap it out prior to deployment… A spare will be available in the field so it is not critical.
    VCSEL – most variables not reporting. SMPLSRINT_VXL 1500 – 2200 (good)
    Cameras – no images being displayed in flight.


    copy_data did not work properly post flight - Janine looking into it.


  2. Joshua Carnes

    May 02, 2026

    GPS Toubleshooting:

    • Josh Turned off Hangar A GPS repeater during pre-flight and the strong 1226 interferer reported by the GPS receiver disappeared.
    • GPS GGQUAL issue occurred at initial takeoff ascent and during final touch/go ascent out of Casper but otherwise did not occur during the other ~8 touch/gos. During GPS issue, GGQUAL changed from 5 to 9 and performance was changing from PPP to SBAS.
    • Josh intentionally changed the GPS receiver ELEVATIONCUTOFF config to 15 degrees during outbound ferry, a setting that remained for the rest of the flight. Although the initial observations supported this being a successful solution because the issue was not observed on many subsequent touch/gos, the re-appearance of the issue on the final touch-go results in a inconclusive or negative test.
    • Novatel Logging was on during the entire pilot pro. This is a good log for further invesigation and submission to Novatel. The log has all binary entries, ~500MB for the ~5hr flight.