Project flight schedule Monday 21 Nov – Friday 23 Dec 5 weeks – 150 flight hours
15
Project flight schedule Monday 21 Nov – Friday 23 Dec 5 weeks – 150 flight hours Closed Thursday 24 Nov – Sunday 27 Nov Normal open hours, Monday - Friday: 6 AM – 7 PM Flight days 8 AM – 4 PM Maintenance days Exceptions TBD 3 – 4 Flight days per week (mostly 10 hours) Focus on more flights early (weather, maintenance)
description
Project flight schedule Monday 21 Nov – Friday 23 Dec 5 weeks – 150 flight hours Closed Thursday 24 Nov – Sunday 27 Nov Normal open hours, Monday - Friday: 6 AM – 7 PMFlight days 8 AM – 4 PMMaintenance days Exceptions TBD 3 – 4 Flight days per week (mostly 10 hours) - PowerPoint PPT Presentation
Transcript of Project flight schedule Monday 21 Nov – Friday 23 Dec 5 weeks – 150 flight hours
Project flight schedule
Monday 21 Nov – Friday 23 Dec
5 weeks – 150 flight hours
Closed Thursday 24 Nov – Sunday 27 Nov
Normal open hours, Monday - Friday:
6 AM – 7 PM Flight days
8 AM – 4 PM Maintenance days
Exceptions TBD
3 – 4 Flight days per week (mostly 10 hours)
Focus on more flights early (weather, maintenance)Remove some instruments before project end (DU, NOAA O3)
Combine objectives to 10-hour flights
Daily flight schedule (Monday-Friday, mountain time)
6:00 Aircraft out, refuel, warm instruments
7:15 All onboard
7:45 Doors close
8:00 Take-off
18:00 Touch-down
18:15 De-brief
19:00 RAF closes down
Changes are possible; e.g. DU-Kent State, MMM-UCLA
objectives
Normal RAF crew duty limits apply (CHECK)
Daily planning schedule (Sunday-Friday)
6:30 Pilot briefing
13:00 Weather forecast (Chris Davis etc.)
Instrument status (all PIs' ground crew)
Flight planning
15:00 Message left on answering machine
Phone 303-497-1040
18:15 De-brief + next day mission update
Daily maintenance schedule (Monday-Friday)assuming 8:00 AM – 6:00 PM flight
6:00 Access to aircraft equipment
- mechanics for paper work
7:00 Equipment must be re-installed
and paperwork completed
- mechanics for paperwork
18:00 Access to aircraft equipment
- mechanics for paper work
19:00 Facility closes
Daily maintenance schedule (Monday-Friday)assuming no flight
8:00 Access to aircraft equipment
16:00 Facility closes
Some flexibility
Notes: with 1-2 no-flight days per week, we have limited
maintenance time.
With 3-4 flights per week, we may need to fly even if some
instruments are 'broken'; - change objectives.
Move rake and inlet once per week on maint. day
Flight areas:
DOCIMS Sr-Cu over Pacific
New Particle SW, NW over Pacific
N over Canada
START N over US and Canada
NW over Pacific
CHAPS Plains, mountains, en-route
Static Defect Anywhere
Dropsondes Testing a few over land
Serial sondes over water
No sondes over Canada
Payload:
Pressure, temperature, dewpoint (lower atmosphere)
Winds (3-10 Hz max., not anti-iced)
Humidity (Campos/Maycom TDL)
Ozone (Gao/NOAA)
CO, CO2 (Campos)
CN, RDMA (Rogers)
Aerosol particles, NMASS, FCAS (Lee, Wilson, LaF.)
Dropsonde (Lauritsen)
Differential GPS (Beaton, Romashkin, Jensen)
Rake + pitotstatic (Friehe, Rogers, Stith)
HIMIL air intakes (Fox, Rogers)
Trailing cone (Jensen, Friesen, Schanot, - Jan 06)
Who can fly:
Must be directly project operations related Equipment operator, flight scientist,teaching if directly project related (Jeff)
Who can fly: 11 seats:2 pilots1 RAF tech1 EOL data system programmer1 dropsonde operator1 RAF trace gas operator1 RAF aerosol operator1 DU aerosol operator2 Mission scientists (1 CHAPS, 1 non-RAF)1 more (instrument training, etc.)
Later we may free up programmer seat
Flight decisions:
Group decision by PIs and delegates at 1 PM planning meeting
Project manager to function as 'circuit breaker' in case of disagreements
Project manager to keep track of time used by eachproject
Project managers: Jensen, Schanot and Romashkin303-497-1028, -1063 and -1027
Data handling
Real-time data feed:Every 5 seconds, data transferred to ground
database (1 Hz data)
Inside UCAR firewall use “aeros”Outside UCAR firewall use web browser(www.eol.ucar.edu/raf/)
Data handling
Chat:
Any client (e.g. xchat)Sign EOL agreementServer for EOL/RDCC: rdcc.guest.ucar.edu/6668Use SSLAccept invalid SSL certificateChat channel: &G5
Nick-name: FirstnameLastname-locatione.g. RonRuth-JeffCo
Use /nick to change your name
Data handling – FTP:
FTP fownload site: ftp.atd.ucar.eduDirectory: /pub/archive/RAF-projects/ProgSciNaming convention for all files you provide:
PS_20051206_0600_instrument.ext PS_yyyymmdd_hhmm_instrument.ext
Subdirectories for specific purposes:data: prelimenary netCDF files from prior flightsimages: data/image to push to G5 during flightsreports: self-evident
Please provide upload plans and data formats
Data handling – FTP:
Web browsing from aircraft:Open browserHome page shows uploaded data
Organization:
Door access cards – add your nameOne card per group (unless special need)
Email and phone list – add your detailsSafety briefing – read carefully and sign formPhoto release – sign form, list permit or no permitComputer usage form - sign
