OPERATIONAL REPORT APRIL/MAY/JUNE Significant AMDAR Problems During Period. Identifier Description Status/Date

Transcription

1 E-AMDAR APRIL/MAY/JUNE 2004 EADAS Significant AMDAR Problems During Period Identifier Description Status/Date Lufthansa data was not processed by the AMDAR system during the period 16/04/04 20/04/04. On the afternoon of the 18th, DWD/Offenbach confirmed that the data (UDAx01 EDZW) were being sent to Met Office. This data should be routed to EADAS for processing and the header changed to EGRR and then sent to the switching system (FROST). A combination of server problems and routing from FROST to the E-AMDAR processing system (EADAS) caused these data flow problems, which are currently under investigation by the system developer and Met Office communications Team. All data from 16th/16:21UTC was queued and forwarded to EADAS for processing. The problems encountered were resolved wef 20th/10:50UTC. 16/04/04 16:21 20/04/04 10:50UTC New routines installed in daily reports to 13/04/04 remove software bug in timeliness matrices. Webserver problem 2505/04 26/05/04 Resolved 26/05/04 Lufthansa (bufr) AMDAR data was received Resolved 06/05/ :00UTC by EADAS due to problems with EADOS 05/05/ UTC UTC. Data restored at 06/05/ :00UTC. Lufthansa data was not processed by the Resolved 17/06/04 AMDAR system during the period 16/06/ UTC 17/06/04 11:15UTC. The problems encountered were resolved wef 17/06/04 11:15UTC and all archived BUFR data sent EADOS EADOS shows 28th and no data available for 29 th. Lido had problems with the receipt of the OBS data. These data are the basis for the E-ADOS optimization. The consequence was sub-hourly profiles. Other important note: 01/04/2004 On 28th Feb (10:07-20:20 UTC) and 29th Feb (16:29-20:27 UTC) was again an interruption of the transmission EGRR to EDZW. A new database procedure had been installed 06/05/ :00 UTC which was not compatible with the database used for EADOS. The result was that EADOS was cut off the operational data. Without operational data EADOS was unable to do an optimisation. KNMI QEv Centre Data processing problems 30/04/04-01/05/04 Resolved 01/05/04 British Airways implementation of the compressed software on the B737 fleet has been further delayed by staff resource shortage at BA - data costs for the short haul fleets Ongoing continues to be monitored closely The problem with ftp transfer to the EADAS WebServer continues (update to monthly graphs etc) The system developer and TC are working on resolving this issue. Ongoing Significant Network Developments During Period Saudi aircraft commenced reporting data evaluated by EUCOS 03/04/ Lufthansa A330 aircraft purchased since October 2003 added to EADOS 10/04/2004 Lufthansa enroute data reporting increased from 10min to 7min frequency 05/04/2004 New Lufthansa aircraft: EU6962 A /04/2004 British Airways data costs agreed for /04/2004 New Lufthansa aircraft: EU6363 A /04/2004 New Lufthansa aircraft: EU6258 A /05/2004 New Lufthansa aircraft: EU6273 new A340 29/05/2004 Finnair preparing to test connectivity to LIDO/EADOS (2x AMDAR equipped B757 a/c May 2004 New Lufthansa aircraft: EU4527 reactivated A300 01/06/2004 New SAS Q400 EU8116 activated - New Universal ACARS MU 11/06/2004

2 New SAS Q400 EU7651 activated - Old Honeywell ACARS MU 11/06/2004 New Lufthansa aircraft: EU6315 A , EU0359 A (after replacement of 16/06/2004 the temp sensor) New SAS Q400 EU /06/2004 E-AMDAR Network Performance Graphs Figure 1: E-AMDAR Timeliness OT+120, Period January 2003 December 2006 Figure 2: E-AMDAR Timeliness OT+45, Period January 2003 December 2006 Figure 3: E-AMDAR Network Development, Period January 2000 December 2006

3 Figure 4: E-AMDAR Number of suspect aircraft error bias (O-B)> T = +/-1.5 K Period January 2000 December 2006 Figure 5: E-AMDAR aircraft totals Period January 2000 December 2006 Figure 6:E-AMDAR Monthly average number of observations against Target

4 ASAP ships OPERATIONAL REPORT Significant ASAP Problems During Period Station Description Status/Date National ASAP Unit Germany: System error at the end of May. Repaired May June 2004 Hornbay (ELML7) 07/06/04 now working and performance has improved at both the 100hPa and 50hPa and targets are being reached. National ASAP Unit Germany: Sealand Motivator (WAAH) Nil observations due to a version error. The vessel was unable to wait in port. May 2004 Docked in Polish shipyard 10/07/04 17/09/04 German Research ASAP Unit: Meteor (DBBH) National ASAP Unit Germany: Sealand Developer (KHRH) National ASAP Units Denmark: Naja Arctica.(OXVH2) Nuka Arctica.(OXYH2) National ASAP Units France: Fort Saint Pierre (FQFM) Fort Saint Louis (FQFL) EASAP Unit: Sealand Performance (KRPD) EASAP Unit: Sealand Achiever (WPKD) Interferences between soundings from German Research Vessel METEOR and Valentia Observatory (southwest of Ireland). METEOR was advised to change frequency. Digicora burnt out due to high voltage replacement ordered. Performance has improved during the second quarter and both the 100hPa and 50hPa targets are being reached Performance has improved during the second quarter and both the 100hPa and 50hPa targets are being reached The two Danish ASAP units have had difficulties achieving the 100hPa and 50hPa because they launch 200g balloons which tends to burst at a lower altitude 300 g balloons will be ordered Jan 2005 and the deployment can start in the middle of A limited supply of 300 g balloons are available at the Danmarkshavn RS station in Greenland. These balloons will be send back to Denmark, However this station is not expected to be accessible until August/September when the ice is gone. However, both units have achieved target in recent months. Fort Saint Louis (FQFL) achieved both targets in May. Fort Saint Pierre (FQFM) is below the 100hPa and 50hPa targets. The launchers on board are briefed about the importance of respecting the protocole of a second launch if the first one stops before 150hPa and no launch when wind is stronger than 40 knots. CMA-CGM Manager of the French fleet informed and monitoring continues. Low Performance due to technical difficulties with sondes. Several relaunches required due to sudden temperature drop to -50C when leaving container. Possible contact with antenna or stack. Due to interference with land stations KRPD advised to take four soundings per day in the Mediterranean. Lower performance than expected due to technical problems caused by satellite communication problems. Soundings successful but not transmitted to LES Low availability due to technical problems with communication. Satellite communications failed. The crew found that LORAN-C works well in the entire area between US East coast and Europe Performance has steadily dropped below the 50hPa target during Q2. None of the 33 June soundings achieved the 50hPa height. The crew has been advised to check balloons and sondes carefully before launching. Equipment and consumables will be checked at the next visit of PMO. May 2004 June 2004 June 2004 May /04/2004 April May 2004 April 2004 April 2004 May 2004 March April 2004 May - June 2004

5 National ASAP Unit United Kingdom: CanMar Pride (ZCBP6) National ASAP Unit Iceland/Sweden: Skogafoss(V2XM) National ASAP Unit Spain: Esperanza del Mar (EBUQ) EASAP Unit: Sealand Performance (KRPD) National ASAP Unit Germany: Sealand Developer (KHRH) National ASAP Units France: OPERATIONAL REPORT Performance has improved during the second quarter and the 100hPa target is now being reached CanMar Pride will continue the St Lawrence soundings at 0600 and 1800 and increase to 3 soundings a day across the N Atlantic (ie at 0000, 1200, and 1800) Performance has been below the 100hPa & 50hPa targets from the beginning of this year due to low sensitivity of the MARWIN. Short docking times in Reykjavik have hampered progress. In addition kit on board is aged and has a tendency to fail. April May 2004 June 2004 Proposed repair of equipment April 2004 MARWIN repaired - good results for one trip. April 2004 Receiver settings had drifted resulting in May/June 2004 lower sensitivity. It has now been corrected. Monitoring continues Performance dropped just below the 100hPa April June 2004 target during April. Performance improved during May and is now on target Significant Network Developments During Period Description Date Route change from the Western Med to the June 2004 Middle East (via Suez). As long as there is no other ship the soundings are to be continued in the Med with 4 soundings per day (one in four weeks round trip). Route change from the US to North Europe June 2004 service to the US to Mediterranean service. It will follow the same route as Sealand Performance (KRPD) previous route. (one week in the western Med). There might be a problem with the helium supply. Programme Manager visited MeteoFrance, June 2004 Trappes to discuss French National units and their future integration. Two in four French units are currently in operation. The third unit will commence operation in The fourth unit is awaiting a ship. ASAP Network Performance Graphs Figure 7: ASAP Network Development:Timeliness. Number of ASAP TEMP soundings received within HH+120 Period January 2003-December 2006

6 Figure 8: ASAP unit Timeliness HH+120 Period January - June 2004 Figure 9: ASAP Network Development based on data received within HH+120 for the purposes of NWP. Period January 2003-December 2006 Figure 10: E-ASAP Network Performance: Percentage of ASAP TEMP achieving 100hPa height. Period January 2003-December 2006

7 Figure 11: E-ASAP Network Performance: Percentage of ASAP TEMP achieving 50hPa height. Period January 2003-December 2006 Figure 12: National ASAP Network Performance:Percentage of ASAP TEMP achieving 100hPa height. Period January 2003-December 2006 Figure 13: National ASAP Network Performance: Percentage of ASAP TEMP achieving 50hPa height. Period January 2003-December 2006

8 Figure 14: ASAP Fleet Network Performance: Percentage of ASAP TEMP achieving 100hPa height EUCOS target of 90%. Period January June 2004 Figure 15: ASAP Network Performance: Percentage of ASAP TEMP achieving 50hPa height EUCOS target of 75%. Period January June 2004 OWS Mike and Ekofisk Significant OWS Mike and Ekofisk Problems During Period Station Description Status/Date Ekofisk oil platform Reduction in availability April June 2004 Significant Network Developments During Period Description Date The Ekofisk oil platform, operated by the Norwegian Met Institute on behalf of Sweden, May 2004 Norway, Germany, the Netherlands and the UK, has been under threat of closure for sometime. The ASAP unit, is currently housed on an old neighbouring platform and the journey to the unit is now unsafe during bad weather. This has been reflected in a noticeable reduction in the number of soundings during the first quarter of Until the unit is relocated to the new platform, it is broadly agreed that only 80-85% availability can be expected, until the old rig closes in 2005 OWS Mike and Ekofisk Network Performance Graphs

9 Figure 16: Ocean Platform Timeliness OT+120. Period January 2003-December 2006 Figure 17: Ocean Platform Data Availability. Period January 2003-December 2006 Figure 18: Ocean Platform Performance: Percentage of soundings achieving 100hPa height against EUCOS Target. Period January 2003-December 2006

10 Figure 19: Ocean Platform Performance: Percentage of soundings achieving 50hPa height against EUCOS Target. Period January 2003-December 2006 RADIOSONDE Significant Radiosonde Problems During Period Station Description Status Lajes (08508) Consistently launch <2 radiosondes/day Ongoing Lisboa (08579) Funchal (08522) Thessalonik (16622) The quarterly availability results for Thessalonika were below the expected target of 95% for the first quarter of 2004, and improved during the second quarter. From April Thessalonika has made three soundings per day. June 2004 Bodo-VI (01152) Nil observations 07/06/04 16/06/04 due to problems with logic controller in the launcher. New power supply, processor and software installed. Resolved UTC Heraklion(16754) A problem with an antenna fault persisted throughout the first Resolved quarter. Availability results for Heraklion were therefore below the expected target of 95% for the first quarter of After the installation of a new antenna there has been a significant improvement. Valentia (03953) Interferences between soundings from German Research Vessel Resolved end May 2004 METEOR and Valentia Observatory (southwest of Ireland). METEOR was advised to change frequency. Bordeaux (07510) Various problems with autosonde since mid March after an 19/05/2004 upgrade by a Vaisala team from RS80 to RS92/loran C standard. Vaisala intervention consisted into an adaptation of mechanical part to operate the new RS92 sondes and in a replacement of DIGICORA 2 by DIGICORA 3 software. After several delays the intervention was finally planned on 15 march Since then there have been problems such as bad launches, incomplete TEMP messages, erroneous wind data and other problems. Vaisala engineer visit arranged for 24.may to install a new version of the LORAN-C digicora exploitation software and also GPS digicora software. Monitoring continues Significant Network Developments During Period Description Date Lajes (08508) USAFE consider the withdrawal of funding to the upper air sounding program of Lajes. The impact of the Lajes observing program on ECMWF and the UK Model is considered and a response made by UK Met Office NWP stating that the current available evidence about the benefit on NWP strongly supports the continuance of such in-situ profile reports to compliment and enhance the utility of data from satellites. Note:No airline is currently providing ascent/descent profile reports at the airport on the island. June 2004

11 Szeged (12982) OPERATIONAL REPORT Hungarian site included within the network monitoring results, prior to inclusion in the Network Design. 09/06/04 * (1) 9 EUCOS sites frequently launch >2 radiosondes /day, (2) 5 EUCOS sites frequently launch <2 radiosondes/ day. (3)** Timeliness used for EUCOS sonde statistics is measured by subtracting the nominal ascent time from the time of receipt. 'nominal ascent time' is defined as a multiple of 3 hours (HH) such that the launch time lies between HH -2 and HH +1. For example, any launch between 10Z and 13Z would have a nominal time of 12Z. Radiosonde Network Performance Graphs Figure 20: Radiosonde timeliness: soundings received within HH+120. Period January 2003-December 2006 Figure 21: Radiosonde: Daily availability of current EUCOS network. Period January 2003-December 2006

12 Figure 22: Radiosonde: Percentage of selected EUCOS radiosondes achieving 100hPa height against EUCOS Target. Period January 2003-December 2006 Figure 23: Radiosonde Performance Percentage of selected EUCOS radiosondes achieving 50hPa height against EUCOS Target. Period January 2003-December 2006 SURFACE LAND Significant RBSN Problems During Period Station Description Status 04270, 04373, 06720, > 1.0 hpa bias outside the EUCOS performance Monitoring continues 08045, 16080, 16684, criteria. Significant Network Developments During Period Description Date Nil Report *The data extraction for the Met Office Global Model runs every six hours, but only extracts data for a three-hour window, so the data in the statistics are for hours 00, 04, 05, 06, 10, 11, 12, 16, 17, 18, 22, 23. Surface Land Network Performance Graphs

13 Figure 24: Surface data availability: Average number of observations used for NWP per day. Figure 25: Surface Data Timeliness Performance Timeliness: Percentage of soundings received within HH+120. Period January 2003-December 2006

14 Figure 26: Surface Data Timeliness Performance Timeliness: Percentage of soundings received within HH+15. Period January 2003-December 2006 Figure 27: Surface Pressure PP(O-B) Bias Period April June 2004 Voluntary Observing Ships Significant VOS Problems During Period Station Description Status Significant Network Developments During Period Description Nil Report # Date In the following histograms all VOS observations reported into the EUCOS area are taken into account, not just those of EUMETNET members. Voluntary Observing Ships Network Performance Graphs

15 Figure 28: Automatic VOS Network Performance: Data Availability. Figure 29: Manned VOS Network Performance: Data Availability. Figure30: VOS Network Performance: Timeliness HH+45

16 Figure 31: VOS Network Performance: Timeliness HH+115 Period January -December 2006 Figure 32: Automatic VOS Data Quality: Percentage of Gross Error Figure 33: Automatic VOS Data Quality: RMS of differences Gross Errors excluded.

17 Figure 34: Manned VOS Network Performance:Data Availability. Figure 35: Manned VOS Data Quality: Percentage of Gross Error. Figure 36: Manned VOS Data Quality: RMS of differences Gross Errors excluded Moored and Drifting Buoys

18 Significant Moored and Drifting Buoy Problems During Period Station Description Status Rarh buoy (WMO 62106) Discussions continue at the Met Office on the future of the and K5 buoy (WMO 64045) UK moored buoy network according to the first drafts of the Non operation E-SURFMAR design study. 07/05/2004 Significant Network Developments During Period Date At April 30 th, 54 EGOS-EUCOS drifting buoys were operational in the North Atlantic (i.e. April 2004 reporting reliable air pressure measurements at least). At the same time, 8 drifting additional buoys, belonging to US agencies, were in operation in the EUCOS area of interest. # Statistics provided by E-SURFMAR *only ten EUCOS moored buoys out of the twelve are operating ** This target corresponds to 40 buoys reporting 90% of hourly data, it replaces a target which was "24 obs/buoy/day".it is in agreement with the present monthly figures and those of other components. This target will be reviewed and approved by PB-OBS Moored and Drifting Buoys Network Performance Graphs Figure 37: Moored Buoy Data Availability. Figure 38: Moored Buoy Data Availability., hourly reports per day (Gross Errors excluded)

19 Figure 39: Moored Buoy Network Performance: Timeliness OT+15 Figure 40: Moored Buoy Network Performance: Timeliness OT+120 Figure 41: Moored buoy Data Quality: Percentage of Gross Error

20 Figure 42: Moored buoy Data Quality: RMS of differences Gross Errors excluded Figure 43: Drifting Buoy Data Availability. Figure 44: Drifting Buoy Data Availability. EUCOS Drifting Buoys. Number of deployments per month.

21 Figure 45: Drifting Buoy Network Performance: Timeliness OT+120 Figure 46: Drifting Buoy Data Quality: Percentage of Gross Error Figure 47: Drifting Buoy Data Quality: RMS of differences Gross Errors excluded