Yep, and nope. That would be a join:
SELECT wfp.plane_name, ynt.destination
FROM yournewtable ynt
INNER JOIN wp_flr_planes wfp ON wfp.id = ynt.planeid
WHERE wfp.plane_name = 'This is the plane name'
I can't really suggest a good query since I don't know what all of your properties are, and I'm not sure how you intend to use it after. I see something like a booking, so a plane has a known name and number of seats, and is used in a booking to see a destination and date/time of departure/arrival, etc.
If you use INNODB database engine, then you can add constraints as well (that are enforced). So in the secondary table, you can specify that it's "planeid" must reference the id in the wp_flr_planes. If it doesn't exist, it will throw an error, and you can set up cascading for updates and deletes.