Airways Magazine

Contact Us

ADVERTISING


CLICK HERE

for more information on ADVERTISING opportunities with Airways Magazine and Airwaysmag.com

 


EDITORIAL


You can contact a writer directly by:

Leaving a COMMENT on a writer’s article

Reaching out to a writer via their SOCIAL ACCOUNTS

Send CORRECTIONS to erratumcenter@airwaysmag.com


For general editorial feedback contact / Submit story pitches to

editorial@airwaysmag.com


MAGAZINE SUBSCRIPTIONS


CLICK HERE

to order NEW and manage existing SUBSCRIPTIONS.

 


Email us with any subscription related questions or concerns

airways@airwaysmag.com


     

PURCHASES


Order Reprints of Articles.
Airways Magazine Back Issues.

CONTACT US!


[contact-form-7 id=”151″ title=”Contact form 1″]

2 Comments

  1. rogerl53@outlook.com
    rogerl53@outlook.com July 19, 08:31

    Dear Airways,

    I particularly enjoyed the “Airlines of Alaska: Part 2” article by David Stringer. In 1965 the very first flight I ever took was on Pacific Northern Airlines. There is a 50/50 chance that the Boeing 720 pictured in the magazine is the same one in my snapshot taken through the window at the gate at Sea-Tac. Imagine that!

    I have another snapshot taken by my father of me at the top of the airstairs in Anchorage as we boarded for our return flight. The puzzle is that the this aircraft was, apparently, one that PNA picked up from Braniff as the main color is ochre. But, I distinctly recall that one being a 707 because of onboard markings. The info I found so far is that the PNA aircraft from Braniff were all 720’s. I found only one vague reference to an ex-Braniff 707 flying with PNA. My photo doesn’t show any registration numbers.

    Is my memory faulty? That would be no surprise after all these years. Were 707 “spare parts” on the 720? Anyway, it is a fun mystery and the article brought back great memories. To top it off, I think I looked rather dapper as a 12 year old in a suit and tie.

    Thanks for a super magazine.

    Roger Lipera

Only registered users can comment.

error: Content is protected !!