In Domain-Driven Design, you should model your aggregate to closely reflect the real-world domain and the invariants you need to enforce.

In your travel planning system, a TravelPlan is an aggregate that can involve multiple associated MemberTravelPlan records(even if in some cases you only have one).

So I think you should store the MemberTravelPlan as a List within your TravelPlan aggregate.