Thank you for correcting the text in this article. Your corrections improve Papers Past searches for everyone. See the latest corrections.

This article contains searchable text which was automatically generated and may contain errors. Join the community and correct any errors you spot to help us improve Papers Past.

Article image
Article image
Article image
Article image

THE- FLYING SQUADRON.

. S;> fur' as can foe made out from the somewhat confused statement in ' our Australian 'telegrams, the Flying Squadron reached Melbourne.', on Xov. -. ; 5, or about thirteen days V.ftcr it m-jis dtie in (he route table issued •tHou the Sjuadron sailed from England. The Squadron will' probably stay ten days ■ or a fortnight at Melbourne, and although Tasmania is not mentioned in the route table ••iiiiiled to, it is quite likely, especially as the Tasnmniaus ardently desire it, that a visit •jv ill be paid to Kobart Town. Sydney is included in the list of place? to be visited, and the date of probable arviyal at Lyttelton !*£-4"au 2in the original table.; Allowing for the .delay in arrival at Melbourne, and for a probable visit to Tasmania, the Squadron cm i'.ardly be looked for here before, say, Jan. '25. Jl'he next steamer from Melbourne may bring ■•'jEe'SuUe information.

Permanent link to this item

https://paperspast.natlib.govt.nz/newspapers/TS18691206.2.5

Bibliographic details

Star (Christchurch), Issue 485, 6 December 1869, Page 2

Word Count
151

THE- FLYING SQUADRON. Star (Christchurch), Issue 485, 6 December 1869, Page 2

THE- FLYING SQUADRON. Star (Christchurch), Issue 485, 6 December 1869, Page 2

Help

Log in or create a Papers Past website account

Use your Papers Past website account to correct newspaper text.

By creating and using this account you agree to our terms of use.

Log in with RealMe®

If you’ve used a RealMe login somewhere else, you can use it here too. If you don’t already have a username and password, just click Log in and you can choose to create one.


Log in again to continue your work

Your session has expired.

Log in again with RealMe®


Alert